Opened 3 years ago

Closed 3 years ago

#2230 closed help (fixed)

Met Office CICE branches

Reported by: apm Owned by: ros
Component: NEMO/CICE Keywords:
Cc: Platform: ARCHER
UM Version:


I am running the GO6.0 NEMO configuration both on Archer (from Puma) and on Monsoon. The Archer version has a bug in the CICE model code, which has been fixed at the Met Office and put into a development branch.

What is the procedure for including a Met Office development branch in a suite on Puma? At present FCM appears not to be able to see the Met Office branches. The branches I would like to use are:


The first is the bug fix, while the other three are updates that I would like to incorporate at the same time.



Change History (5)

comment:1 Changed 3 years ago by ros

  • Component changed from UM Model to NEMO/CICE
  • Owner changed from um_support to ros
  • Platform set to ARCHER
  • Status changed from new to accepted
  • UM Version <select version> deleted

Hi Alex,

These branches all appear to be in the new MOSRS CICE repository so are immediately available to FCM. Add the branches as you have listed above into the "CICE sources" box and it should pick them up. If this doesn't work please let me know the suite id and I'll take a look.


comment:2 Changed 3 years ago by apm

Hi Ros,

I just added Alex West's mod into my suite (u-an485), and got this error:

[FAIL] svn://puma/NEMOCICE_svn/CICE/branches/dev/alexwest/r134_fix_warm_lowest_layer_crash@160: not found
[FAIL] svn: warning: W170000: URL 'svn://puma/NEMOCICE_svn/CICE/branches/dev/alexwest/r134_fix_warm_lowest_layer_crash' non-existent in revision 160
[FAIL] svn: E200009: Could not display info for all targets because some targets don't exist

[FAIL] fcm make -f /home/apm/cylc-run/u-an485/work/19580101T0000Z/fcm_make_ocean/fcm-make.cfg -C /home/apm/cylc-run/u-an485/share/fcm_make_ocean -j 4 mirror.prop{}=2 # return-code=2
Received signal ERR
cylc (scheduler - 2017-07-25T15:08:34Z): CRITICAL Task job script received signal ERR at 2017-07-25T15:08:34Z
cylc (scheduler - 2017-07-25T15:08:34Z): CRITICAL failed at 2017-07-25T15:08:34Z

Do I need to add something into the "CICE Sources" box to tell ROSE where to find the the MOCI development branches?



Last edited 3 years ago by ros (previous) (diff)

comment:3 Changed 3 years ago by ros

Hi Alex,

Ok, so in order to use those new branches you will need to switch your suite to using the CICE MOSRS repository for all your other branches rather than the old PUMA hosted one.

All the other branches you have specified in the suite have an equivalent on the CICE MOSRS repository. See the CICE wiki page:

I've checked the revision numbers for each of the branches against the Met Office internal branches and they are as listed in the above pages. So you can just replace with the external location specified in the tables. E.g. branches/dev/jwalton/vn5.1.2_avoid_NEMO_units_UKMO@5381 will become branches/dev/jamierae/vn5.1.2_avoid_NEMO_units@98.

Once you've done that you then need to change cice_project_location to be fcm:cice.xm which points to the MOSRS CICE mirror repository.


comment:4 Changed 3 years ago by apm

Hi Ros,

Thanks - that was exactly what I needed to know! The suite has now compiled and is waiting to run.



comment:5 Changed 3 years ago by ros

  • Resolution set to fixed
  • Status changed from accepted to closed
Note: See TracTickets for help on using tickets.