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
I was running the logging module with area-based logging approach and found no direct mortality at all. I tracked down to this line of code. As for area-based logging, cur_harvest_tag is set to 2, thus there will never be direct logging mortality resulted from it.
This tag was designed to be 0 for C-based harvest if biomass match the demand or area-based harvest. Later I have changed this to 2 for area-based harvest thus it can bypass some of the harvest debt calculation in patch dynamics. Thanks for the correction. Will contact others and submit PR for correction.
sshu88
added a commit
to sshu88/fates
that referenced
this issue
Nov 20, 2024
fates/biogeochem/EDLoggingMortalityMod.F90
Line 346 in 08f2410
I was running the logging module with area-based logging approach and found no direct mortality at all. I tracked down to this line of code. As for area-based logging, cur_harvest_tag is set to 2, thus there will never be direct logging mortality resulted from it.
fates/biogeochem/EDLoggingMortalityMod.F90
Line 283 in 08f2410
this condition check should be (cur_harvest_tag .eq. 0 .or. cur_harvest_tag .eq. 2).
The text was updated successfully, but these errors were encountered: