-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
CICE writing extra restarts #175
Comments
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. |
Thanks Siobhan. I guess the advantage here is we should only need to set the restart interval in one place ( |
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. |
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. |
In Its hard to map the We can add a note to |
Hi @anton-seaice This sounds like a sensible compromise, I guess when the model is doing longer runs under payu or rose/cylc control the values will also be controlled with settings from there to be across all the component models together, and in the test phase, users may be setting different options, but need to know if they are set centrally in nuopc.runconfig. |
Thanks @ofa001 - my assumption is most of the time, users won't want to write "extra" restart files, i.e. other than at the end of a run? If during longer runs writing extra restarts without restarting the model is common, then maybe its not the best compromise? |
Hi @anton-seaice, during test runs we tend to save more restarts, it also is useful if we want to go back and get additional high frequency data. Sub daily say, for downscaling in the atmosphere, hourly for ice stats in ice and ocean. However its often the other way we often want to clean up runs ( like we are doing on ik11) and restarts are the first thing that we clean up in long production runs, drop back to 10, 20 year intervals. So I guess choose I sensible setting but document on how to change it relatively easily. |
It looks like CESM might put in a fix too , which means we can get all the settings through the CICE CMEPS driver. ESCOMP/CICE#29 |
UFS have put a fix in: In future |
Per ESCOMP/CICE#29 we can set |
I tested both So we can just remove |
…ion (#169) * License file * Update incorrect note in MOM_override See COSIMA/access-om3#251 Co-authored-by: minghangli-uni <[email protected]> * Add non-default from MOM_parameter_doc.layout in the middle reorder MOM_input to follow MOM_parameter_doc.short Put non-default values from MOM_parameter_doc.debugging at the top Co-authored-by: Dougie Squire <[email protected]> * Add WIND_STAGGER to MOM_INPUT for clarity This only affects the logging, the actual value is hardcoded through a #ifdef CESMCOUPLED * Change atm and ice mesh from 1deg -> 025deg Change ice_ntasks to be 96 Remove unused components payu-org/payu#496 Removed some checks in Payu which required unused components to be present in the nuopc.runconfig file. Co-authored-by: Dougie Squire <[email protected]> * Update to ACCESS-NRI/ACCESS-OM3 deployment 25.01.0 * Update field dictionary with latest from CMEPS * add_gusts parameter needed for 0.4.0 build * Update nuopc.runconfig to turn-off dates in restart_pointers * Turn on netcdf4 per COSIMA/access-om3#81 The new build uses openmpi4.1.7, which fixes some bugs preventing parallel reads over symlinks. This allows use of parallelio netcdf4 option, even though at this resolution for most components we will still only use one PE for IO. * Use .d and .m in CICE history output filenames Per COSIMA/access-om3#201 * Turn off extra cice restarts and remove non functioning write_restart_at_endofrun per COSIMA/access-om3#175 * Set Earth radius the same as the UM * Update MOM6 parameters and docs See COSIMA/access-om3#274 --------- Co-authored-by: anton-seaice <[email protected]> Co-authored-by: Dougie Squire <[email protected]> Co-authored-by: Anton Steketee <[email protected]> Co-authored-by: dougiesquire <[email protected]>
Remove dump_freq from the ice_in file has been completed in dev- branches : 1deg_ryf ACCESS-NRI/access-om3-configs#161 And will be captured in #283 and #284 And payu is no longer setting the restart time, see payu-org/payu#556 |
TL;DR: The CICE cmeps driver is not using the restart settings from
nuopc.runconfig
and is using those fromice_in
Using 1deg_jra55do_iaf I set:
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:
The correct restart was saved here:
The PBS error log also has this error from:
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 innuopc.runconfig
?The text was updated successfully, but these errors were encountered: