CICE writing extra restarts

[anton-seaice]

TL;DR: The CICE cmeps driver is not using the restart settings from nuopc.runconfig and is using those from ice_in

Using _1deg_jra55doiaf I set:

 restart_n = 5
 restart_option = nyears
 stop_n = 5
 stop_option = nyears

in nuopc.runconfig

I then ran access-om3 (access-om3-d6813d6b9e1df560ac3f6ba6a605daab9cfd9569_main-5pjh7z2) using payu 1.1.3. The model completed and ran succesfully.

The archive/output000 folder incorrectly contained:

archive/output000/access-om3.cice.r.1959-01-01-00000.nc  archive/output000/access-om3.cice.r.1960-01-01-00000.nc  archive/output000/access-om3.cice.r.1961-01-01-00000.nc  archive/output000/access-om3.cice.r.1962-01-01-00000.nc

The correct restart was saved here:

archive/restart000/access-om3.cice.r.1963-01-01-00000.nc

The PBS error log also has this error from:

./archive_cice_restarts.sh: line 4: [: too many arguments

This is because CICE is writing annual restarts due to these settings (from ice.log):

dumpfreq = y x x x x (set in ice_in) dumpfreq_n = 1 1 1 1 1 (the default)

I think the desired behaviour in the cmeps driver for CICE ignores/replaces and values from ice_in and sets them from the values in nuopc.runconfig ?

[ofa001]

Hi @anton-seaice I don't understand enough about the cmeps driver to be of help here Anton, I guess I am used to everything being under control of what's in ice_in hence CICE settings, but I guess across a coupled system we want to try and control it the same way the cmeps system has set it up and have similar approach to how MOM6 is controlled. I doubt we will be able to control the UM through cmeps though Martin Dix/Kieran Ricardo might know more.

[anton-seaice]

Thanks Siobhan. I guess the advantage here is we should only need to set the restart interval in one place (nuopc.runconfig) and then it is propagated consistently to MOM/CICE/WW + the mediator without needing to set the same information in multiple places.

[ofa001]

Yes if we can set it once for the CICE6-MOM6-WW3 set up that would be an advantage, so that it runs the same in all 3 models.

The coupling with the UM cmeps side will be a more complex set up that I am not fully across, just helping out with the fluxes, coupling fields and looking at the output side.

[MartinDix]

Our intention for CM3 is that settings in the rose/cylc suite set CMEPS and model control namelists consistently. We did this with OASIS in CM2 with driver scripts that modified the namelists.