-
Notifications
You must be signed in to change notification settings - Fork 9
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
+Missing Pointers for Benthic Fluxes in Direct Sinking of Phytoplankton P #19
Conversation
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.
Thanks for implementing this Yi-Cheng. It looks good to me. If we could run just confirm conservation in the 1D case, that would be great.
Thanks Yi-Cheng, In answer to your question about the iron, this was indeed intentional. The iron flux to the sediment is removed. The flux from the sediment is then set using a published relationship: ocean_BGC/generic_tracers/generic_COBALT.F90 Lines 9903 to 9906 in bfa0211
|
Thanks @charliestock . I believe the relationship is from Dale et al. 2015, is that correct? I will add more detailed inline documentation to highlight this. |
@charliestock . Thanks. I can confirm with this fix, the total P is conservative in the 1D case by checking |
This PR passed the CI test and has proven mass conservation for P in the 1D case. Merge now. |
As @charliestock suggested, now the pointers for the benthic fluxes for the direct sinking of phytoplankton P are set correctly in
generic_COBALT_update_from_bottom
subroutine. This PR is to solve #18.@charliestock , While reviewing the
generic_COBALT_update_from_bottom
subroutine, I noticed that pointers for the benthic fluxes for the direct sinking of phytoplankton Fe are also turned off. Below is an example for diazotroph Fe:ocean_BGC/generic_tracers/generic_COBALT.F90
Lines 7707 to 7708 in 01f7a0c
Could you confirm if this was done intentionally?