Setup Rose/cylc environment on PUMA: puma$ export PATH=/home/fcm/bin:$PATH
puma$ . ~fcm/setup_cylc
Or add these lines to your ~/.profile or ~/.kshrc and reload your environment.
Start up the Rosie suite browser: puma$ rosie go
In the search box enter "KPP" and click the "search" button. Suite puma-aa119 should appear.
The Rose edit GUI should appear.
Exploring the suite settings: The left hand panel is your navigation window and lists a tree of pages that make up this suite.
Left click the triangles to expand the tree, right click them to expand everything.
suite info - contains the suite discovery info. Generated when a suite is created.
suite conf – defines inputs to the cylc suite configuration files. In here under “KPP host” I have added options to specify remote host and user id.
fcm_make_kpp – is currently just a placeholder, that eventually would contain the configuration for building a new KPP executable if desired.
kpp - All the settings for the KPP namelists are under here.
Go to kpp -> namelist. Left click on “Top level model control”. This will open the page as a tab in the main (right hand) panel. You can also middle click to open a page as another tab (as in Firefox).
The “Top level model control” page contains all the items that can be set in the NAME_TIME namelist and “Coupling controls” is the NAME_COUPLE namelist.
You will see the namelist variable listed and below that is a helpful description of what that variable is. If you left click on a variable some addition help text can be displayed.
Looking at the “Coupling controls” panel I have tried to demonstrate some of the features that can be added. For example if you switch l_cplwght to false the edit box to specify a coupling weight file will disappear. It is also possible to specify a range of valid values for a variable. Try changing climice_period to a negative number – red warning triangles should appear in the left hand panel and the entry in the “Coupling Controls” page should also turn red.
Blue dots appear in the left hand panel to indicate changes made since the last save. Pages can be reverted to their saved state by clicking the “Revert page to saved” toolbar button.
Change the userid and remote directory location: Go to suite conf -> KPP host. Change REMOTE_USERID to be your ARCHER username.
Go to kpp -> env. Change NML_ROOT_DIR to be your /work directory on ARCHER.
Save your changes by clicking the save toolbar button (2nd from the left) or going to the File menu.
This only saves your changes locally and is not overwriting my suite in the subversion repository.
Checking against UMUI job: The suite contains some example macros that perform basic checking against the UM job associated with the suite, to show what can be done.
Go to kpp -> env and set the value of UMUI_JOBID to point to a UM job. This job should have been PROCESSed by you – so have a directory under ~/umui_jobs, which is what the macro looks at. (As a simple test, copy ~annette/umui_jobs/xlnja to your ~/umui_jobs/)
Then click on the Metadata menu and then kpp. Two macros should appear:
kpp/um.UmChecker.validate: This checks the start date in this suite (startt) matches the start date of the UM job and reports an error if not.
kpp/um.UmChecker.transform: This overwrites the start date in the suite with that of the UM job. It reports the changes it will make and asks whether you want to make the changes.
Try running each of these macros.
Running the suite: Assuming you have ssh-agent set up to login to ARCHER without needing to enter a password/passphrase you can now try running the suite.
In theory you should be able to run the suite by clicking the grey triangle on the toolbar, but it’s not currently working on PUMA for some reason. Instead you will need to navigate to the suite directory that will have been created at ~/roses/puma-aa119 when you launched the rose edit GUI.
Once in this directory type:
This should launch the suite to create the 3D_ocn.nml namelist and copy it over to your directory on ARCHER. Currently I have set the install script to append the suite id (e.g. puma-aa119) to the namelist filename so you can immediately see with which suite it is associated. A cylc GUI will pop up and hopefully briefly show the running suite, before finishing with “stopped with succeeded” in the bottom information bar. If all has gone well you should now have the file /work/n02/n02/[userid]/hadgem3-kpp/kpp_namelists/3D_ocn.nml.puma-aa119 on ARCHER.