Updated default fates parameter file for new api 8.1.0 format. #870
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
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
This PR is synced with NGEET/fates#595
Changes here should only update the default fates parameter file location.
Tag info will be added last in Externals_CLM.cfg after tests pass and FATES side changes are integrated.
Specific notes
See: NGEET/fates#595
Are answers expected to change (and if so in what way)?
Since the parameter files are different, I don't think this will pass b4b tests, even though the values are all the same in the parameter file, and answers should not change. The parameter names have changed, and new parameter entries have been added that are not used yet.
Any User Interface Changes (namelist or namelist defaults changes)?
Testing performed, if any:
fates test suite, results TBD