Skip to content
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

[BUG/ISSUE] Incorrect source of Be7Strat and Be10Strat below tropopause level in RnPbBe extension #59

Closed
lizziel opened this issue Nov 2, 2020 · 1 comment
Assignees
Labels
category: Bug Something isn't working
Milestone

Comments

@lizziel
Copy link
Contributor

lizziel commented Nov 2, 2020

In the HEMCO RnPbBe extension, emissions for species Be7Strat and Be10Strat are set to the emissions for Be7 and Be10 at and above the tropopause level each time the Emissions component is run. This is done in the following code:

          IF ( L > ExtState%TropLev%Arr%Val(I,J) ) THEN
             IF ( Inst%IDTBe7Strat > 0 ) THEN
                Inst%EmissBe7Strat (I,J,L) = Add_Be7
             ENDIF
             IF ( Inst%IDTBe10Strat > 0 ) THEN 
                Inst%EmissBe10Strat(I,J,L) = Add_Be10
             ENDIF
          ENDIF

Because the tropopause level can change per column per timestep, and because emissions are not reset to zero below the tropopause level, there can be accumulated sources directly below the tropopause for Be7Strat and Be10Strat over time. For example, if TropLev goes up one level for a given column then the previous emission value at the level below the new TropLev persists and is erroneously applied again. This continues until a new TropLev is at or below the original TropLev. The result is an over-estimate of Be7Strat and Be10Strat.

This bug also introduces small differences between model output when breaking up a single segment transport tracer simulation into multiple consecutive runs, such as is done for the GCHPctm transport tracer benchmark.

@lizziel lizziel added the category: Bug Something isn't working label Nov 2, 2020
@lizziel lizziel added this to the 3.0.0 milestone Nov 2, 2020
@lizziel lizziel self-assigned this Nov 2, 2020
@lizziel
Copy link
Contributor Author

lizziel commented Nov 2, 2020

This issue is fixed in HEMCO commit 4468b68. It will be included in the 3.0.0 release that accompanies the 13.0.0 release of GEOS-Chem.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category: Bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant