-
Notifications
You must be signed in to change notification settings - Fork 92
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
bb_slope is read from parameter file, but overwritten prior to use #73
Comments
would explain the surprising lack of a bb_slope effect in Elias and @xuchongang's sensitivity study? |
yeah, I stumbled across some old notes I had on this, and combined with their results, prompted me to revisit the code |
Yeah, this was just re-engineered in CLM5. You're correct on all counts. It
|
ok, its a simple fix, sounds like we are all in agreement |
There is another parameter that is somewhat coupled in with the slope parameter: Ball-Berry minimum leaf conductance, unstressed (umol H2O/m**2/s). Is this cuticular? We are using some two values hard-coded for C3 and C4 plants. Is there interest in adding these as PFT parameters to the parameter file? @rosiealice , @xuchongang , others? |
Ryan, Yours On Tue, Jun 14, 2016 at 2:14 PM, Ryan Knox [email protected] wrote:
|
Actually, this would be great. Danica has a paper on the impact of minimum On 14 June 2016 at 15:24, chonggang xu [email protected] wrote:
Dr Rosie A. Fisher Terrestrial Sciences Section |
applied corrections, PR to come, testing |
Merge branch 'rgknox-bbfix-careafix-icefiltfix' This PR bundles 3 fixes that address: #73, #69, #44 The fix to 73 is the only one that would be expected to have b4b regressions. I performed baseline simulation comparsisons between f1a14d6 and 18613d1, and tests confirmed b4b on all expected passes. One extra step was necessary, in that I needed to update the parameter file values of BB_slope to match what was previously hard coded (a value of 9). The current value in the default parameter file is 8, we can certaintly change this going forward. Not changing this now. The other two fixes, #69 and #44 are not supposed to generate b4b results, and they don't. 1x1 brazil simulations were also run on eddi to make sure that the non-b4b changes continue to generate very similar projections of forest composition and structure, as well as flux variables. They did. Fixes: #73 Fixes: #69 Fixes: #44 User interface changes?: no Code review: rgknox Test suite: ed - lawrencium-lr3 intel, eddi (PC) gnu (visualizations); ed - yellowstone gnu, intel, pgi Test baseline: 18613d1 Test namelist changes: none Test answer changes: yes, see above Test summary: pass except for #14 known failures in f09 and f19 restart, and gnu f10 restart #43.
Summary of Issue:
bb_slope (stomatal slope, as per BBF photosynthesis lore) is read from the parameter file, indexed by PFT. This parameter is supposedly used by EDPhotosynthesis. The parameter file value is stored in bb_slope, and it is transferred to mbb. bb_slope is used no-where else in the code.
Around line 360:
So bb_slope is used to populate mbb. However mbb is then over-written in the next patch loop, and had not been used prior to the over-write. At roughly 404 of EDPhotosynthesis:
Where you can see above, that the actual parameters being used are two values from Gordon Bonan's paper. Not that those values aren't reasonable, but we should decide where we want the values set.
As far as I can tell, these are values for C3 and C4 pathways.
The two values are 9 (C3 I think) and 4 (C4), the paper is Bonan et al. 2011, JGR, 116, doi: 10.1029/2010JG001593
I think what happened is that when bb_slope was added to the code as a user controlled parameter, the coder just didn't see that the mbb variable was set twice. It actually isn't used in the first appearance.
My recommendation is that we simply remove the first call to mbb and bb_slope, and change the line I flagged "FIX POINT" to:
Have discussed this issue with @xuchongang
What is the changeset ID of the code, and the machine you are using:
all to current
The text was updated successfully, but these errors were encountered: