Mdtf support #25
Merged
Mdtf support #25
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
|
@ceblanton I expect the other PR to have merge conflicts once we merge this in though not too much to handle. So, either order for the two open PRs would be ok.. but mdtf support is a simpler PR with no fre-cli implications, and might make sense to merge in first. |
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 branch has support for the new MDTF pre-processor.
time_range populated,
standard_name filled in with mappings,
gfdl to cmip frequencies conversion done
CI tests updated, see manifest in actions workflow and download the csv to see how it looks.