-
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
removed slascaler and various fates parameter changes #287
Merged
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
Here is the cdl format of the fates parameter file Here is a diff of the parameter file:
|
ckoven
approved these changes
Oct 10, 2017
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.
Looks great to me. Thanks @rgknox
This was referenced Oct 10, 2017
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The calculation of leaf biomass was being scaled by the ratio of a parameter slascaler, and slatop. However, this ratio is redundant with the allometric slope parameter. The ratio was removed, and the parameter was removed from the parameter read.
Other wish-list changes to parameters were added to this PR, including: 1) addition of understory collateral damage fraction for logging 2) addition of dbh_repro_threshold, which sets the size where clonal reproduction kicks in, 3) changed max_dbh to allom_dbh_maxheight which is more consistent with the meaning, 4) carbon to biomass multiplier which converts mass in carbon to mass in total biomass.
The dbh_repro_threshold is set equal to allom_dbh_maxheight in the file for now; and while it is read-in, the value is not used until modular allometry is introduced. The understory collateral damage fraction for logging was set to the natural survivorship fraction, again this is read-in but not used.
PR is coupled with fates-clm PR# 27 (https://github.com/NGEET/fates-clm/pull/27 )which updates the default file
Code review:
Test suite: ed.cheyenne.intel , ACRE comparison for 100 year simulation at 4 ngee tropics sites
Base fates Hash: b6b3a86
Base fate-clm hash: 4b4c5a4
Test namelist changes: none
Test answer changes: EXPECTED (part bug fix on bleaf and its derivative, parameters modified to reduce differences)
Test summary: ed.cheyenne.intel: expected PASS, nlcomp and base compares expected FAILS