use unity normalization; add error catch if more than one normalization type is specified#41
Merged
DeniseWorthen merged 2 commits intoApr 27, 2021
Conversation
* switch to using unityone normalization in ufs for all fields * add model abort if more than one normalization type is specified for a single n1:n2:maptype
Merged
13 tasks
junwang-noaa
approved these changes
Apr 20, 2021
binli2337
approved these changes
Apr 20, 2021
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.
Switch to using unityone normalization in ufs for all fields
Add model abort if more than one normalization type is specified for any n1:n2:maptype
CMEPs Issues:
#38
#40
Description of changes
esmFldsExchange_nems_mod.F90fromnonetoone