-
Notifications
You must be signed in to change notification settings - Fork 318
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ctsm5.3.022: Update FATES namelist and build options to avoid Meier2022
#2934
Open
glemieux
wants to merge
8
commits into
ESCOMP:master
Choose a base branch
from
glemieux:fates-meier-bldcheck
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+19
−6
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
If fates is on, default to ZengWang2007, otherwise use Meier2022
5 tasks
glemieux
commented
Jan 14, 2025
ekluzek
added
enhancement
new capability or improved behavior of existing capability
priority: high
High priority to fix/merge soon, e.g., because it is a problem in important configurations
FATES
A change needed for FATES that doesn't require a FATES API update.
science
Enhancement to or bug impacting science
non-bfb
Changes answers (incl. adding tests)
size: small
test: aux_clm
Pass aux_clm suite before merging
test: fates
Pass fates test suite before merging
labels
Jan 14, 2025
ekluzek
requested changes
Jan 14, 2025
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for working on this @glemieux and getting this in quickly. We'll talk Thursday on where this should go in upcoming tags.
I ask for a couple changes that are easy.
5 tasks
ekluzek
reviewed
Jan 15, 2025
This was referenced Jan 15, 2025
this avoids the need to set a `.true.` condition for z0param_method in the defaults
…h fates" This reverts commit 43407e1.
ekluzek
changed the title
Update FATES namelist and build options to avoid
ctsm5.3.022: Update FATES namelist and build options to avoid Jan 16, 2025
Meier2022
Meier2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
enhancement
new capability or improved behavior of existing capability
FATES
A change needed for FATES that doesn't require a FATES API update.
non-bfb
Changes answers (incl. adding tests)
priority: high
High priority to fix/merge soon, e.g., because it is a problem in important configurations
science
Enhancement to or bug impacting science
size: small
test: aux_clm
Pass aux_clm suite before merging
test: fates
Pass fates test suite before merging
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
Avoid running
fates
withz0param_method=Meier2022
in light of #2932.Specific notes
Contributors other than yourself, if any:
CTSM Issues Fixed (include github issue #):
Does the first step in #2932
Are answers expected to change (and if so in what way)? Yes, for fates compsets with
Clm60
Any User Interface Changes (namelist or namelist defaults changes)? Yes, changes default for roughness for FATES and disallows one option when FATES is used
Does this create a need to change or add documentation? Did you do so? No
Testing performed, if any: will do regular and fates tests suites