Add ability to use noleap calendar with gregorian forcing files - #33
Open
dougiesquire wants to merge 1 commit into
Open
Add ability to use noleap calendar with gregorian forcing files#33dougiesquire wants to merge 1 commit into
dougiesquire wants to merge 1 commit into
Conversation
…files Only adds support to override gregorian with noleap for now. The opposite aborts
This file contains hidden or 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
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.
This PR adds an optional
calendar_overrideentry todate_manager_nmlinaccessom2.nml. When set, it takes precedence over the file-derived calendar for both the forcing and experiment clocks. Onlycalendar_override='noleap'against gregorian forcing is supported - the existing noleap date-skipping logic already handles this correctly, dropping Feb 29 records. The reverse (calendar_override='gregorian'against noleap forcing) aborts for now.Contributes to #32