add megan compatibility with fates #98
Closed
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
Also makes it accessible from table of contents. Not actually changing file contents at this point.
* The experience of making a mesh from an input with 1d vs. 2d coordinates is identical, so only provide one example. * In example, use as input file the 5x5_amazon surface dataset included with CTSM. * Various wording and typo fixes.
…t fire emission factors datasets
…le and just use the local n_pfts variable that matches the name on the dataset
Avoids requiring new fsurdat.
Fix handling of finidat with cold starts
…an_cherrypick_ctsm_mvertens
Fix handling of finidat with cold starts
…he system if you update to ceps1.0.58
|
Closing since this is the wrong branch to merge to. Should be noresm not master. |
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
Megan changes without the fire emissions commits.
Specific notes
Same notes as the previous now closed PR
#74
Contributors other than yourself, if any:
CTSM Issues Fixed (include github issue #):
#36
Are answers expected to change (and if so in what way)?
Yes, all the MEG_* fields will change, but nothing else.
Any User Interface Changes (namelist or namelist defaults changes)?
No
Does this create a need to change or add documentation? Did you do so?
Yes, but haven;'t changed yet pending further coupled model testing.
Testing performed, if any:
Ran the following test command:
./create_test --xml-category aux_clm_noresm --xml-machine betzy --baseline-root ~/baselines/ctsm_develop --generate noresm2_5_alpha08 --test-id ctsmpr1 --project nn9039k -o
All the other tests passed.