Get Rose

Rose is a framework for managing and running control suites (in our case, specifically JULES control suites). If you are using the Met Office Virtual Machine then this will already be installed so no need to follow these steps.  If Rose has already been installed on your system, please do ROSE_EXEC=$(which rose);ROSE_INSTALLDIR=(${ROSE_EXEC%/*}/..) , substitute all occurrences of ~/.local/rose below with what you see from echo $ROSE_INSTALLDIR and then skip step 1.

 

** PLEASE NOTE that you will need versions of Cylc, Rose and FCM that can work together: see here for how to select them **

 

The instructions here are for creating a local installation of Cylc (because often users will not have permission to create a global installation):

 

STEP 1: Install using this command from a bash terminal:

   cd ~/.local

   git clone https://github.com/metomi/rose.git

   cd rose
   git tag -l

(you can see from the list that the right tag name is "2018.02.0" for Rose release 53)
   git checkout tags/2018.02.0
   cd ..
   rose --version

   cd ..

 

STEP 2: You need to configure Rose before you can use it, which involves generating files at ~/.metomi/rose.conf (in your profile) and at ~/.local/rose/etc/rose.conf (in the Rose installation):

   mkdir ~/.metomi

Next, create a textfile ~/.metomi/rose.conf containing this text (but substituting your username instead of tobymarthews and whatever your SITE is instead of cehwl1 (if you will be engaging in Rose stem testing **)):

[rosie-id]
prefix-username.u=tobymarthews
 
[rose-stem]
automatic-options=SITE=cehwl1

 

** Omit the rose-stem bit if you will not be using Rose stem testing (it is only necessary for code development). Just for information, the SITE setting can (currently) be one of meto, vm, cehwl1, jasmin, niwa or nci (i.e. a selection of UK Met Office internal and UM partners) and tells the system where essential KGO files are stored on those systems ('Known Good Output'), however if you are not engaging in Rose stem testing then you don't need those files and therefore don't need that rose-stem bit.

 

Next, create a textfile ~/.local/rose/etc/rose.conf (or rather $ROSE_INSTALLDIR/etc/rose.conf) containing this text:

 

[rosie-id]
prefix-default=u
prefixes-ws-default=u
prefix-location.u=https://code.metoffice.gov.uk/svn/roses-u
prefix-web.u=https://code.metoffice.gov.uk/trac/roses-u/intertrac/source:
prefix-ws.u=https://code.metoffice.gov.uk/rosie/u
 

STEP 3: Now you need to append the Rose command set to your library. This must be done every time you log on, so best to add the following line to the end of your ~/.bashrc file to accomplish this:

export PATH=$HOME/.local/rose/bin:$PATH

Run your .bashrc file (or log off and log in again):

   . ~/.bashrc

 

STEP 4: Finally, check the Rose installation and server links. Putting in your MOSRS password should give you a hello back from the MetO server:

   rosie hello

 

All done: Rose should be installed.

 

OPTIONAL STEP 5: If you have a PUMA account, you can add the following to .metomi/rose.conf as well (after prefix-username.u; substituting your PUMA username instead of tobymarthews):

prefix-username.puma=tobymarthews
 
and add the following to .local/rose/etc/rose.conf :
prefix-location.puma=svn://puma.nerc.ac.uk/roses_puma_svn
prefix-web.puma=https://puma.nerc.ac.uk/trac/roses_puma/intertrac/source:
prefix-ws.puma=http://puma.nerc.ac.uk/rosie/puma
 

There are lots of other options you can insert into the Rose configuration, by the way (see ~/.local/rose/etc/rose.conf.example for examples): this is a minimal file to get it started. Specifically, however, please do NOT insert anything like “meta-path=...” into ~/.local/rose/etc/rose.conf because this only causes confusion (it's overridden by the meta data specification in your JULES namelists anyway so has no effect).