fix problem with dglc restart interval #499
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
changed the title
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.
Description of changes
fix problem with no coupler file written at restart interval
Specific notes
In the following test ERP_Ln9.ne30pg3_ne30pg3_mtn14.NF1850.betzy_intel.cam-outfrq9
where the compset is 1850_CAM%DEV%LT%NORESM%CAMoslo_CLM51%SP_CICE%PRES_DOCN%DOM_MOSART_DGLC%NOEVOLVE_SWAV_SESP
the glc coupling interval is forced to be the atm coupling interval (i.e. 48) but at the same time the run sequence is forced to be that glc is only called at the end of the run sequence. With this fix - the forcing is removed and there is no longer a descrepancy between the glc coupling interval and the run sequence. This now fixes the ERP test where the compset has DGLC%NOEVOLVE.
Contributors other than yourself, if any: None
CMEPS Issues Fixed:
Are changes expected to change answers? should be bfb
Any User Interface Changes (namelist or namelist defaults changes)? the run sequence will be different for tests
Testing performed
Verified that ERP_Ln9.ne30pg3_ne30pg3_mtn14.NF1850.betzy_intel.cam-outfrq9 now works