-
Notifications
You must be signed in to change notification settings - Fork 27
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
Stop running 0th timestep #67
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.
Thank you for the change @olyson. Please remove the comments. They are forever preserved in github.
@olyson I assigned you because you worked on this, not because i need something from you at this time. |
time in hist now equals the middle of the time_bounds MOSART equivalent to CTSM work done in ESCOMP/CTSM#2838 Answers change only for the time variable. slevis resolved conflicts: src/riverroute/RtmHistFile.F90 src/riverroute/RtmTimeManager.F90
@olyson I have @jedwards4b approval here, but mosart's timemanager changed since you worked on this, such that the line |
I guess the function itself (is_first_step) has been removed since this PR was first issued, so that seems ok. I don't see any other instances of nstep that need modification. |
derecho izumi |
Changes needed to stop running 0th timestep.
See CTSM issue ESCOMP/CTSM#925 and PR ESCOMP/CTSM#2084