v3 single forcing configurations not including all historical greenhouse gas warming effect in hist-GHG #6837
Assignees
Labels
Comments
wlin7
added a commit
that referenced
this issue
Dec 6, 2024
) Revise forcing specifications for single forcing compsets Revisions to single-forcing compsets' forcing specification focusing on where to include the GHG warming contribution of CH4, N2O, and O3 due to v3atm's interactive chemistry. Core to the changes is to separate the transient aerosol and chemical precursors for different single forcing compsets. New virtually transient forcing files are introduced to satisfy the unified data stream control for surface and elevated emissions. Historical evolution of stratospheric ozone is moved from the all-else configuration to the GHG only configuration. Fixes #6837 [BFB] non-BFB only for single forcing compsets [NML] Different only for single forcing compsets
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The original single forcings configurations put historical evolution of chemical precursors in
hist-aer, covarying with arosol precursors, and stratospheric ozone changes (via the associated chlorine and linoz data) inhist-xGHG-xaer(all-else). As a result,hist-aerincludes the warming due to tropospheric ozone changes related to the evolution of chemical precursors;hist-xGHG-xaerinclude the warming effect due to evolution of stratospheric Ch4, N2O and stratospheric and tropospheric ozone. This led to less than expected warming inhist-GHGcompared to the v2 counterpart, more than expected reduction in cooling compared to the v2 counterpart ofhist-aer, and a significant warming effect starting mid-to-late 20th century inhist-xGHG-xaerthat was not seen in v2.To be more comparable with the v2 single-forcings configurations, all the apparent GHGs induced warming effect need to be included in the
hist-GHGconfiguration. The other configurations need to be adjusted accordingly.This is addressed by #6790.
The text was updated successfully, but these errors were encountered: