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 just noticed a small bug in the calculation of GCHP transport tracer budget table in https://github.com/geoschem/gcpy/blob/main/gcpy/budget_tt.py
It looks like the emissions diagnostics in GCHP transport tracer should be flipped (surface layer at 72nd layer), which is not reflected in the calculation of the budget table.
It will only affect the source flux in the table. As a result, the source in GCC for Be7 is around 0.11 g/d, while that in GCHP is only 0.045 g/d .
I tested flipping the vertical dimension can get the source flux comparable with GCC, so hopefully it is the reason.
The text was updated successfully, but these errors were encountered:
Thanks for reporting this @1Dandan. I have transferred the issue to the gcpy repository since it is an issue with the code there. We will try to address this soon.
This issue has been automatically marked as stale because it has not had recent activity. If there are no updates within 7 days it will be closed. You can add the "never stale" tag to prevent the Stale bot from closing this issue.
What institution are you from?
Washington University in St. Louis
Description of the problem
I just noticed a small bug in the calculation of GCHP transport tracer budget table in https://github.com/geoschem/gcpy/blob/main/gcpy/budget_tt.py
It looks like the emissions diagnostics in GCHP transport tracer should be flipped (surface layer at 72nd layer), which is not reflected in the calculation of the budget table.
It will only affect the source flux in the table. As a result, the source in GCC for Be7 is around 0.11 g/d, while that in GCHP is only 0.045 g/d .
I tested flipping the vertical dimension can get the source flux comparable with GCC, so hopefully it is the reason.
The text was updated successfully, but these errors were encountered: