-
Notifications
You must be signed in to change notification settings - Fork 345
Add a FATES namelist option for land use transition logic #3728
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
base: master
Are you sure you want to change the base?
Changes from all commits
a5efb18
819a84e
caa106e
782c977
66189be
62e0961
a8fc8d1
08999a5
ef1ffc8
2a838fb
72a9074
3a176e5
0e02bcb
33c68e0
37ebbc7
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -332,6 +332,7 @@ module clm_varctl | |
| ! > 1 for external data (lightning and/or anthropogenic ignitions) | ||
| ! see bld/namelist_files/namelist_definition_clm4_5.xml for details | ||
| logical, public :: use_fates_managed_fire = .false. ! true => turn on managed fire | ||
| integer, public :: fates_lu_transition_logic = -9 ! controls logic around transition between land use classes | ||
|
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Does the code check and make sure it was changed from the default value of -9? And that it's within the right range in the Fortran code? The namelist scripts ensure it's between 1 and 9, but the Fortran code should as well.
Collaborator
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I've added a check in the CLMBuildNamelist to check for valid values: https://github.com/JessicaNeedham/ctsm/pull/4/changes#diff-c5398a7bf444c79516bff3ba46c0fcc5789d003af843d18b96448d2624d27b18 Is that accomplish what you're thinking about here @ekluzek? |
||
| logical, public :: use_fates_tree_damage = .false. ! true => turn on tree damage module | ||
| character(len=256), public :: fates_harvest_mode = '' ! five different harvest modes; see namelist definition | ||
| character(len=256), public :: fates_stomatal_model = '' ! stomatal conductance model, Ball-berry or Medlyn | ||
|
|
||
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.
It's not currently in the FATES UG. And I didn't see documentation changes in the FATES PR for this (or is the FATES UG located in a different repo?).
The FATES PR does point to Table 1 in this paper:
https://gmd.copernicus.org/articles/13/3203/2020/
which does explain it. So pointing to that table might be the best thing here.
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.
I think you are going for a principle of having the documentation in one place, which is a good goal. It's just that right now that place doesn't exist, so we need a source that can be looked up. It's also easier for users if it is in place and has more visibility. So it's more usable, but less maintainable. But, I also think this is a part that is unlikely to change -- except maybe on a future CMIP cycle. So even though it means duplicating some of this across HLM's the goal of making it easier for users might be OK
Although another thing that could be considered is to tell the user what FATES Fortran code file to look at. Although that's again something that can be changed out from under the documentation here. So I'm not sure the best way of doing this.
Uh oh!
There was an error while loading. Please reload this page.
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.
I think pointing the user to the FATES user's guide should be the most direct option. I added an issue to the FATES user's guide to make sure we get documentation on this there: NGEET/fates-users-guide#110
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 @glemieux , I will add changes to FATES documentation to your PR.
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.
@ekluzek we've updated the user's guide to describe the various options via NGEET/fates-users-guide#111. @JessicaNeedham added the table that corresponds to the valid values.