User specified history write frequency #353
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
nmizukami
added
cesm-coupling
nmizukami
changed the title
ekluzek
approved these changes
Mar 29, 2023
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.
User can specify output write frequency with new control variable
<outputFrequency> daily ! output frequency: integer for multiple of simulation time steps or daily, monthly or yearlyOther minor changes:
maximum IRF unit-hydrograph future time steps are detected and used for dimension size in restart file
TO-DO (near future work):
Need to implement reading accumulated value and number of accumulation time steps in restart reading routine to properly restart. This reading is only necessary when accumulation time steps in restart is not zero (i.e., previous run stop before it write out).
This should be backward compatibility.