Skip to content
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

Copying cice_in.nml to restart dir is confusing #140

Open
aidanheerdegen opened this issue Nov 22, 2018 · 1 comment
Open

Copying cice_in.nml to restart dir is confusing #140

aidanheerdegen opened this issue Nov 22, 2018 · 1 comment

Comments

@aidanheerdegen
Copy link
Collaborator

aidanheerdegen commented Nov 22, 2018

Currently the cice5 driver copies the cice_in.nml from the work directory to the restartXXX directory as it contains model timing information that is needed to correctly restart CICE.

cice_in.nml is also a configuration file, so it is confusing that a file named the same is in two places.

The relevant information required to correctly restart CICE5 should be extracted from cice_in.nml and saved to a new namelist file in the restart directory. Say cice_restart.nml. This is clearer from a user point of view. Especially when the error pops up that payu can't find cice_in.nml when trying to restart an old run, where cice_in.nml was assumed to be in the correspondingoutputXXX directory, but that directory no longer exists.

@aidanheerdegen
Copy link
Collaborator Author

aidanheerdegen commented Dec 7, 2020

@nichannah I am looking into this

I would like to solve #193 using this approach, but I am confused about what timing information ACCESS-OM2 is currently using from cice_in.nml. I am using 1deg_jra55_ryf as a test run, with the runtime set to 1 month, so the first time it runs there is no difference, and then each subsequent run istep0 is incremented by 35040, which is what npt is set to in cice_in.nml.

But if we look in the ice_diag.d files, it seems this is all being ignored

$ grep istep0 archive/output00?/ice/ice_diag.d
archive/output000/ice/ice_diag.d:  istep0                    =        0
archive/output001/ice/ice_diag.d:  istep0                    =      496
archive/output002/ice/ice_diag.d:  istep0                    =      944
archive/output003/ice/ice_diag.d:  istep0                    =     1440
archive/output004/ice/ice_diag.d:  istep0                    =     1920
$ grep npt archive/output00?/ice/ice_diag.d
archive/output000/ice/ice_diag.d:  npt                       =      496
archive/output001/ice/ice_diag.d:  npt                       =      448
archive/output002/ice/ice_diag.d:  npt                       =      496
archive/output003/ice/ice_diag.d:  npt                       =      480
archive/output004/ice/ice_diag.d:  npt                       =      496

So is any of this stuff necessary? Seems like libaccessom2 is taking care of all of this, and we can do away with the reading from the previous cice_in.nml completely.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant