Stop running 0th timestep #37
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@jedwards4b you reviewed and approved the mosart equivalent of this (ESCOMP/MOSART#67) so would you be willing to confirm that this is also ready to approve? |
jedwards4b
reviewed
Nov 11, 2024
jedwards4b
approved these changes
Nov 11, 2024
time in hist now equals the middle of the time_bounds RTM equivalent to CTSM work done in ESCOMP/CTSM#2838 Answers change only for the time variable.
|
@jedwards4b from your message that this is like mosart and that you approved I understand that I can go ahead and resolve your question and prepare to merge. Let me know if I misunderstood. |
|
derecho testing
|
|
This is now rtm1_0_83 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Changes needed to stop running 0th timestep.
See CTSM issue ESCOMP/CTSM#925 and PR ESCOMP/CTSM#2084