#2092 closed help (answered)

ROSE fcm make not compiling

Reported by: avanni Owned by: um_support
Priority: normal Component: Rose
Keywords: Cc:
Platform: UM Version: <select version>



I have been trying to add a branch to my ROSE nesting suite job which is located at


the runid is u-ak234.
When I fist added the branch the suite ran but the changes did not take affect. I spoke to Grenville and he advised that I remove the following lines from my suite-runtime-build.rc file:

ROSE_APP_OPT_CONF_KEYS = "glm" (twice)

Now the code doesn't compile and I am getting the following errors:

[FAIL] config-file=/work/projects/sgwex/avanni/cylc-run/u-ak234/work/20150101T0000Z/fcm_make_glm/fcm-make.cfg:3
[FAIL] config-file= - svn://puma.nerc.ac.uk/um.xm_svn/main/trunk/fcm-make/meto-xc40-cce/um-atmos-high.cfg@7660:1
[FAIL] config-file= - - svn://puma.nerc.ac.uk/um.xm_svn/main/trunk/fcm-make/meto-xc40-cce/inc/um-atmos.cfg@7660
[FAIL] svn://puma.nerc.ac.uk/um.xm_svn/main/trunk/fcm-make/meto-xc40-cce/inc/um-atmos.cfg@7660: cannot load config file
[FAIL] svn://puma.nerc.ac.uk/um.xm_svn/main/trunk/fcm-make/meto-xc40-cce/inc/um-atmos.cfg@7660: cannot be read
[FAIL] svn: E000110: Unable to connect to a repository at URL 'svn://puma.nerc.ac.uk/um.xm_svn/main/trunk/fcm-make/meto-xc40-cce/inc/um-atmos.cfg'
[FAIL] svn: E000110: Can't connect to host 'puma.nerc.ac.uk': Connection timed out

in my log file.

I am not sure why. Can anyone help?



Change History (3)

comment:1 Changed 12 months ago by ros

Hi Annelize,

On exvmsrose command line can you try running

fcm ls svn://puma.nerc.ac.uk/um.xm_svn/main/trunk/fcm-make/meto-xc40-cce/inc/um-atmos.cfg@7660

It should return with the line um-atmos.cfg

What do you get?

I've just taken a copy of your suite and it completes fcm_make_glm fine for me, so there's nothing wrong with the suite setup.

Be careful about removing the ROSE_APP_OPT_CONF_KEYS = "glm" as this will change the defs used in the compilation for glm which may not be what you want. I don't know what conversation you had with Grenvile, so this may be fine for what you want. By removing this you now have an extra def switched on C98_1A=c98_1a.


comment:2 Changed 12 months ago by avanni

Hi Ros,

I have only just seen your message. I managed to get the suite running by copying the suite-runtime-build.rc from another suite run by simon vosper and by removing the ROSE_APP_OPT_CONF_KEYS = "glm" line. It seems to be doing the right thing now and my altered code is in the extract folder.

What are the dangers in removing this line?

Thanks a lot,


comment:3 Changed 12 months ago by grenville

  • Resolution set to answered
  • Status changed from new to closed


In your case ROSE_APP_OPT_CONF_KEYS overrides settings in the rose gui. The gui said include several branches, but these were ignored by the CONF_KEYS, so by removing this, you are undoing a decision made by the person who added it — it's hard to say what the dangers are; it is true to say the models with and without are different.


Note: See TracTickets for help on using tickets.