You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The local variable fates_woodproduct_flux appears to default to zero in the diagnostic output prior to the endrun call associated with the write statements. It should report the results of the summation that it represents.
General bug information
CTSM version you are using: ctsm5.1.dev157
Does this bug cause significantly incorrect results in the model's science? No, this is diagnostic info for a failure condition
Details of bug
The fates_woodproduct_flux is a local variable that is calculated within the column loop inside CBalanceCheck:
Note that it is a summation of site-level fates bc_out variables, that are dependent on the site to column mapping. Later down the code, if the error threshold is met, the variable is used in the diagnostic write statements:
Since the code loops through all columns before reporting the error, there is no guarantee that the fates_woodproduct_flux will be the value corresponding to the failure case.
Important details of your setup / configuration so we can reproduce the bug
I found this while regression testing #2076 with use_fates_luh = .true. using fates commit ea24aa8 and ctsm commit e8b0508.
Important output or errors that show the problem
Error message in lnd.log:
3864 column cbalance error = 1.537941879714219E-006 7
3865 is fates column? = T
3866 Latdeg,Londeg= 30.0000000000000 260.000000000000
3867 begcb = 911.965299656670
3868 endcb = 911.957395544391
3869 delta store = -7.904112279447872E-003
3870 --- Inputs ---
3871 fates litter_flux = 0.000000000000000E+000
3872 fates wood product flux = 0.000000000000000E+000
3873 --- Outputs ---
3874 hr = 7.904112279464640E-003
3875 -1*som_c_leached = -3.964367563847151E-014
3876 iam = 0: local column index = 7
3877 iam = 0: global column index = 5224
3878 iam = 0: global landunit index = 1953
3879 iam = 0: global gridcell index = 865
3880 iam = 0: gridcell longitude = 260.0000000
3881 iam = 0: gridcell latitude = 30.0000000
3882 iam = 0: column type = 1
3883 iam = 0: landunit type = 1
3884 ENDRUN:
3885 ERROR: ERROR in CNBalanceCheckMod.F90 at line 406
Adding statements to write out the wood product during the loop shows the following:
Brief summary of bug
The local variable
fates_woodproduct_flux
appears to default to zero in the diagnostic output prior to theendrun
call associated with the write statements. It should report the results of the summation that it represents.General bug information
CTSM version you are using: ctsm5.1.dev157
Does this bug cause significantly incorrect results in the model's science? No, this is diagnostic info for a failure condition
Details of bug
The
fates_woodproduct_flux
is a local variable that is calculated within the column loop insideCBalanceCheck
:CTSM/src/biogeochem/CNBalanceCheckMod.F90
Lines 313 to 314 in bf19eb8
Note that it is a summation of site-level fates
bc_out
variables, that are dependent on the site to column mapping. Later down the code, if the error threshold is met, the variable is used in the diagnostic write statements:CTSM/src/biogeochem/CNBalanceCheckMod.F90
Line 375 in bf19eb8
Since the code loops through all columns before reporting the error, there is no guarantee that the
fates_woodproduct_flux
will be the value corresponding to the failure case.Important details of your setup / configuration so we can reproduce the bug
I found this while regression testing #2076 with
use_fates_luh = .true.
using fates commit ea24aa8 and ctsm commit e8b0508.Important output or errors that show the problem
Error message in lnd.log:
Adding statements to write out the wood product during the loop shows the following:
The text was updated successfully, but these errors were encountered: