-
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
Scaling of cohort crown area in the output files? #1126
Comments
@mpaiao I think it is the same conversion? i.e. multiplying by Lines 76 to 77 in 5551a70
fates/main/FatesConstantsMod.F90 Lines 223 to 224 in 5551a70
|
@ckoven Thanks for clarifying. In the short term, I will replace But maybe we can have a long-term discussion on whether or not to even have a nominal area at some point. If nplant is defined as a true demographic density (stems m−2), then the site area is not really needed for anything, and it would reduce the number of multiplication operations in the code. |
@mpaiao agreed, that would be nice (but also will probably touch everything!) |
This addresses issue NGEET#1126
I am adding a new crown area variable to the output (by size class and PFT). I was trying to build on existing variables in FatesHistoryInterfaceMod.F90, but I am somewhat confused. When defining crown area by size class, the cohort variable is scaled by
1 / m2_per_ha
:fates/main/FatesHistoryInterfaceMod.F90
Lines 3386 to 3387 in 5551a70
fates/main/FatesHistoryInterfaceMod.F90
Lines 3535 to 3536 in 5551a70
However, when defining crown area by PFT, the cohort variable is scaled by
AREA_INV
:fates/main/FatesHistoryInterfaceMod.F90
Lines 3041 to 3048 in 5551a70
Is there any reason for the different scaling, or should both be scaled by
AREA_INV
?The text was updated successfully, but these errors were encountered: