ctsm5.4.039: add new fates namelist switch for dbh init when nocomp is on#3910
ctsm5.4.039: add new fates namelist switch for dbh init when nocomp is on#3910mvdebolskiy wants to merge 7 commits into
Conversation
|
Per the ctsm-fates standup this morning, @mvdebolskiy is going to add a test for the new namelist option that will update the |
|
@glemieux Should I also add an SP test? |
Not at this point, I think. It currently wouldn't end up doing anything since during initialization fates sp mode calculates the initial dbh from a hard-coded height value: Maybe there is a case to allow the user to change this initial dbh directly instead of calculating it from using the satellite phenology data, but I don't think so (at least not at this point). It would also require a bit of refactor to the sp mode initialization calls. CC'ing @adrifoster for her thoughts. |
Fix for FATES year-boundary restart issue
|
Starting |
Merge b4b-dev to master Details in PR ESCOMP#4000
|
|
|
Regression testing on Results: I've updated the |
|
|
||
| Changes answers relative to baseline: | ||
|
|
||
| sb |
There was a problem hiding this comment.
This looks like an accidental add?
There was a problem hiding this comment.
Good catch, yep that's accidental
| } | ||
| my $var = "use_fates_dbh_init"; | ||
| if ( &value_is_true($nl->get_value($var)) && ( !&value_is_true($nl->get_value("use_fates_nocomp")))) { | ||
| $log->fatal_error("$var can only be .true. use_fates_nocomp is .true." ); |
There was a problem hiding this comment.
We should add a failure test for this in the build-namelist tester.
There was a problem hiding this comment.
I've got this updated and tested on derecho; I'll push it once it's back online.
|
It looks like jobs on Derecho timed out. But, the following ones are listed as pending still: Izumi all looks fine. I didn't check the fates tests. |
ekluzek
left a comment
There was a problem hiding this comment.
There's a simple change to add a test to the build-namelist tester.
A bigger thing that I think would be worth thinking about is how this option should work with finidat files. If I understand this right this only applies if CLM_FORCE_COLDSTART==off. If that's the case we might want to add some more checking around this. I think that might be easy to do, but we'd probably want to it in a different PR since the testing is almost complete here. I can make an issue around this and it could be something for b4b-dev in the next go around.
|
@ekluzek this is only used in coldstart. (you can check call sequence in fates: |
Description of changes
This change is coordinated with FATES PR NGEET/fates#1550.
Adds a switch for initializing patches with dbh instead of density for nocomp runs.
Specific notes
Contributors other than yourself, if any:
CTSM Issues Fixed (include github issue #):
Are answers expected to change (and if so in what way)?
No, switch is off by default
Any User Interface Changes (namelist or namelist defaults changes)?
use_fates_dbh_iniis added.Does this create a need to change or add documentation? Did you do so?
Testing performed, if any:
Passed with diffs when
use_fates_dbh_init=.true.Without that namelist change bfb.
NOTE: Be sure to check your coding style against the standard
(https://github.com/ESCOMP/ctsm/wiki/CTSM-coding-guidelines) and review
the list of common problems to watch out for
(https://github.com/ESCOMP/CTSM/wiki/List-of-common-problems).