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

REST_OPTION=nsteps not working correctly #443

Closed
jedwards4b opened this issue Mar 21, 2024 · 0 comments · Fixed by #447
Closed

REST_OPTION=nsteps not working correctly #443

jedwards4b opened this issue Mar 21, 2024 · 0 comments · Fixed by #447
Assignees

Comments

@jedwards4b
Copy link
Collaborator

I don't believe that the mediator is correctly triggering RESTART writes. In the following case I get restart files for all components except rof and cpl.

create_newcase --case f.cam6_3_144.ne30.datest --res ne30pg3_ne30pg3_mg17 --compset FMTHIST --run-unsupported
./xmlchange REST_OPTION=nsteps
./xmlchange REST_N=12
./xmlchange STOP_OPTION=nsteps 
./xmlchange STOP_N=24 
./xmlchange DOUT_S=FALSE

I think that the issue is in the way that the restart timestep is calculated, from the mediator log I see:
(med_phases_restart_alarm_init) restart clock timestep = 10800
Which I believe is based on the ROF_NCPL=8. We don't see this issue in the tests because the tests reset
ROF_NCPL=48 prior to running to allow the test to have a shorter overall length.

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

Successfully merging a pull request may close this issue.

2 participants