FCM (Flexible Configuration Management) is a code management tool that essentially does two jobs: firstly, it's your tool for dealing with the JULES version-control system, and, secondly, it deals with the compilation of the JULES model too. If you are using the Met Office Virtual Machine then this should already be installed so no need to follow these steps. If FCM has already been installed on your system, please do FCM_EXEC=$(which fcm);FCM_INSTALLDIR=(${FCM_EXEC%/*}/..) , substitute all occurrences of ~/.local/fcm below with what you see from echo $FCM_INSTALLDIR and then skip step 1.

Installing FCM means you have also installed Subversion, which FCM uses to deal with version control internally, so there will be no need to install Subversion as well even if you get any error messages saying "svn command is not found" later on.




** 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 FCM (because often users will not have permission to create a global installation):


STEP 1: Install using these commands from a bash terminal

   cd ~/.local

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


STEP 2: You need to link your FCM Subversion repository to the MOSRS (this is explained here). Two possibilities here: type

   ls ~/.subversion/servers


STEP 2a: If this says ‘No such file or directory’ then you have not used Subversion before on this system so you need to create that .subversion/servers file:

   mkdir ~/.subversion

Create a textfile ~/.subversion/servers with the following lines (substituting your MOSRS username instead of tobymarthews):


metofficesharedrepos = code*



username = tobymarthews

store-plaintext-passwords = no


STEP 2b: Alternatively, if you have used Subversion on this system before then you need to modify the textfile at ~/.subversion/servers: find the [groups] and [metofficesharedrepos] sections and amend them to have the extra few lines specified above (remembering to substitute the correct MOSRS username), leaving the rest of the file unmodified.

   *** Potential problem *** if your existing version of Subversion is pre-vn1.9 then your MOSRS password may not cache properly and you may need to add another repository following instructions similar to these, but please take advice from a System Administrator in this case to be sure you do not disturb the existing svn installation.


STEP 3: Now you need to append the FCM 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/fcm/bin:$PATH

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

   . ~/.bashrc


STEP 4: Check the FCM installation using:

   fcm --version


STEP 5: Set up keywords as described here (which is necessary to get Rose Stem working, but also saves a bit of typing). Do this by creating a textfile on your system at ~/.metomi/fcm/keyword.cfg containing these lines:
location{primary, type:svn}[jules.x] =
browser.loc-tmpl[jules.x] ={1}/intertrac/source:/{2}{3}
browser.comp-pat[jules.x] = (?msx-i:\A // [^/]+ /svn/ ([^/]+) /*(.*) \z)

location{primary, type:svn}[jules_doc.x] =
browser.loc-tmpl[jules_doc.x] ={1}/intertrac/source:/{2}{3}
browser.comp-pat[jules_doc.x] = (?msx-i:\A // [^/]+ /svn/ ([^/]+) /*(.*) \z)


STEP 6: Not finished yet: you need also to cache your MOSRS password in order to be able to use FCM, as described here. There are two options: GNOME keyring (Seahorse) and GPG Agent. The instructions here are for GPG agent only.


** CACHING YOUR MOSRS PASSWORD may be problematic on Fedora 23 systems and/or if your MOSRS password has special characters in it: please email JULES support if you encounter problems **


Download two MOSRS utilities from here:


Put in your MOSRS password, save the file and close Firefox.


Again, put in your MOSRS password, save the file and close Firefox.

   mv ~/Downloads/mosrs-setup-gpg-agent ~/.local/mosrs-setup-gpg-agent

   mv ~/Downloads/mosrs-cache-password ~/.local/mosrs-cache-password

   chmod 777 ~/.local/*

   export PATH=$HOME/.local:$PATH

Now activate (n.b. you need to have installed Rose first before this can work):

   . mosrs-setup-gpg-agent

You should be asked to put your MOSRS password in more than once and then you’ll be told your Subversion and Rosie passwords have been cached (on the first time through you may need to log out and log back in more than once to make this work). To test this has worked correctly, you should find that you are NOT asked for your password when you type in the following commands:

   rosie hello

   svn info --username=tobymarthews

(just to be clear: if you get a response from rosie hello and the svn command WITHOUT having to type in your password then your password is cached correctly. If it works, but asks you for your password then you've got Rose and FCM installed correctly, but it's missing or can't access one or other of your profile files so rewind a few steps and try again).


You will need to re-cache your MOSRS password every time you log in from now on. It’s easiest to accomplish this by adding the following lines to the end of your .bashrc file (n.b. the command with square brackets in it won't display properly on this webpage so I've uploaded an image instead and you must type that bit in):

export PATH=$HOME/.local:$PATH

 #Stop if not running interactively (see MetO advice from )
. mosrs-setup-gpg-agent

(if you log out and log in again, you should find that it now asks you for your MOSRS password and informs you that your subversion and rosie passwords have been cached: if none of that happens then one possibility is that your system has only been set up to run .bash_profile on logon rather than .bash_profile and .bashrc and you can change that setting with these commands

   cd $HOME

   ln -s .bashrc .bash_profile

which create a softlink to achieve this. If the ln command returns "File exists" then instead edit your existing .bash_profile file to add this

   . $HOME/.bashrc

on the end of it, which should be enough).