-
Notifications
You must be signed in to change notification settings - Fork 6
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
Restart at eor #31
base: dev/unified
Are you sure you want to change the base?
Restart at eor #31
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this looks okay - except for asking why the get_min_timestep is in wave specfic code when it could be in the general share code?
model/src/wav_shr_mod.F90
Outdated
update_nextalarm = .true. | ||
! call ESMF_ClockGet(clock, TimeStep=AlarmInterval, rc=rc) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why keep the comment?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
removed
model/src/wav_shr_mod.F90
Outdated
character(len=CS) :: cvalue | ||
integer :: comp_dt ! coupling interval of component | ||
integer, parameter :: ncomps = 8 | ||
character(len=3),parameter :: compname(ncomps) = (/"atm", "lnd", "ice", "ocn","glc","rof", "wav", "esp"/) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why is this routine in wav share code and not in the general share code? I thought there was actually a routine now in share that could deal with this.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
removed
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Other than @mvertens's comments, lgtm.
I have addressed her comment, and tested the change. I will push it back now. |
Pull Request Summary
Adds support for cesm write_restart_at_endofrun
Description
Denise Worthen may want to review. The stop and restart alarm initialization order needs to be reversed this is in support of setting a restart alarm based on the stop time. A new function get_minimum_time is needed in wav_shr_mod to correct timestamp errors when using _OPTION=nsteps.
Issue(s) addressed
Commit Message
The CESM options REST_OPTION=nsteps, STOP_OPTION=nsteps and HIST_OPTION=nsteps were not properly set by WW3. The component model needs to know the minimum model coupling time in order to correctly set this option.
Check list
Testing