-
Notifications
You must be signed in to change notification settings - Fork 105
Grass phenology update #554
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
Grass phenology update #554
Conversation
…fates param read in
…fates parameter file
…al_veg_ready_to_merge_July_2019
… DBH threshold value for cold induced leaf/stem drop
… of the stem drop to the fates parameter file
|
My local branch of this PR is failing on the exact restart test for the mpi-serial library. It looks like |
|
@LuZhai @xuchongang I noticed in EDInitMod that the Lines 506 to 522 in bfe83fd
whereas in FatesInventoryInitMod, there is matching code for both stress and seasonality in fates/main/FatesInventoryInitMod.F90 Lines 1045 to 1065 in bfe83fd
Should EDInitMod have the initialization code for |
|
@glemieux , good catch and we need to let EDInitMod have the initialization code for sapwmemory and structmemory for deciduous stress. |
Thanks; I'll add it on my local branch. I fixed the restart error as well just now. New PR coming to your branch sometime later today. |
|
That was interesting. I somehow added labels using keyboard shortcuts. That's what I get for using two screens and not paying attention to both |
|
@glemieux, thanks and I did not see the pull request on my branch yet. |
|
@xuchongang apologies for the delay. I spoke too soon; I wanted to wait for the test to complete, which was held up until the weekend in the Cheyenne queue. The test passed and I've created the PR to your branch. |
Xu coast veg head fix
|
@glemieux, thank you and I have made the merge of your pull request. |
|
Testing update: All standard testing passed B4B with the default parameter file (i.e. I also ran a parallel 5 year test at Brazil with and without the stem drop fraction greater than zero (in this case I set all PFTs to a randomly selected value of 0.25). Output comparison plots run through the ACRE suite can be found here: https://drive.google.com/file/d/1Bj5gBPf7a13bvrG7X01ho2V6jCaiimBL/view?usp=sharing |
|
At @ckoven I plotted out the From this and the cprnc output it looks like the problem is just with the one grid cell, for this time point at least. @rgknox suggestion I've got a longer term f45 grid running to see if the errors grow. Barring an expansion of the diff to other grids and/or the increase in the difference, do you think this is reasonable to merge, @xuchongang ? |
|
@glemieux , for me, it is fine to merge..... |
|
@rgknox had another thought on what might be causing the non-B4B results even when the stem drop parameter is zero. The flushing logic looks like it could possibly flush only a portion of the At this suggestion, I added a check during the flush to use all of the This indeed resulted in B4B results. The question is, should we be using |
|
@glemieux , I think "using totalmemory for leaves when stem drop is zero" sounds reasonable to me. |
Add stem drop fraction check for flushing
|
Final testing results. All expected PASS: |


This pull request update the phenology for grass. Namely, to drop stems during cold or drought conditions.
Description:
We made the following key modifications:
Collaborators:
Lu Zhai, [email protected]
Expectation of Answer Changes:
For grass, it will change the phenology if phen_stem_drop_fraction set to values > 0. Otherwise, it should generate the same output as before.
Checklist:
Test Results:
Not yet
CTSM (or) E3SM (specify which) test hash-tag:
CTSM (or) E3SM (specify which) baseline hash-tag:
FATES baseline hash-tag:
Test Output: