Add MAPL ExtData format option required in MAPL 2.26.0 #1489
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
This is a required update for use with MAPL 2.26.0 Signed-off-by: Lizzie Lundgren <elundgren@seas.harvard.edu>
56a8538 to
0b71f75
Compare
This was referenced Nov 7, 2022
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 pull request is part of a group of pull requests to update MAPL from 2.18.3 to 2.26.0 in GCHP. See instructions here:
geoschem/GCHP#265
The version update includes a new capability to read the ExtData component configuration file in yaml format. The GCHP
CAP.rcconfiguration file is required to specify which format to use, using new entryUSE_EXTDATA2G. If true, a yaml file is expected. If false, the traditionalExtData.rcfile is expected. We do not yet have a yaml version of the ExtData config file for GCHP so the switch is set to false by default.