-
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
issue with growth respiration calculation #1194
Comments
Just wanted to note that we discussed this on a call last week and decided that we really should be using the daily integrated difference between GPP and maintenance respiration as the basis for growth respiration. And so will change the code to do that. The expectation when we do so is two things will change:
|
4 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Last week, @JessicaNeedham and I were discussing growth respiration, and we noticed that the growth respiration calculation may not be doing exactly what is intended. the key line is here:
https://github.com/NGEET/fates/blob/main/biogeophys/FatesPlantRespPhotosynthMod.F90#L998-L999
The issue is the
max(0._r8, gpp-mr)
part. while it makes sense to not let growth respiration go negative at night, adding the zero floor to this means that, integrated over a whole day/night cycle, GR != grperc*(GPP-MR), it only equals that over the part of the day when GPP > MR. And this high frequency growth respiration gets integrated through thenpp_tstep
term over the day to result in the total carbon available to grow with. So as a result, I think we are likely overestimating the growth respiration and thus underestimating the NPP relative to what we intend for a given value of thegrperc
parameter. Unless thegrperc
parameter is only intended to be applied during the day, but I don't believe that is the case. So if the intention is that the grperc parameter is meant to be applied over both day and night, we should reformulate this expression (somehow, not sure exactly best how to, that can be a later part of the discussion).The text was updated successfully, but these errors were encountered: