Skip to content

Conversation

1Dandan
Copy link

@1Dandan 1Dandan commented Aug 6, 2025

Name and Institution (Required)

Name: Dandan Zhang
Institution: Harvard University

Describe the update

As the feature of scaling grid boxes with specific value from a text file in HEMCO does not work with GCHP, as stated in a ticket of geoschem/GCHP#432, I modified the HEMCO code to apply gridded scaling factor based on the value of state vector ID at geoschem/HEMCO#330. This update of HEMCO would work for both GCC and GCHP. Thus, to minimize the differences between IMI-GCC and IMI-GCHP for synchronizing updates later, I modified the code for creating Jacobian runs in IMI-GCC as well.
To work with IMI specific configs, the changes made at geoschem/geos-chem#2893 need to be incorporated to make it work properly for creating Jacobian run directories.

Note:

  • The perturbation scaling factor starting at 2000 would interfere with the scaling factors used in CEDS 0.1 for carbon simulations, and thus modify it to start at 3000.

Expected changes

There is no difference (except rounding error) of using this branch from the default, but applying this branch would help minimizing the differences between IMI-GCC and IMI-GCHP for the sake of future update synchronization.

Using IMI-GCC version 2.2.0 at 2x2.5 for testing. The visualization notebooks from the default and this branch show negligible difference:
visualization_notebook.zip

Also to check the perturbation runs, I output the emissions for a perturbation run, which is supposed to have 1e-8 target emissions over a certain pixel (state vector element), and 0 elsewhere.
The emissions for an example state vector ID 3000 (zoom in to see near the Horn of Africa) by default (ref) and using this branch (dev):
image

Additional note - preparation of the test run:

@1Dandan 1Dandan changed the title To use gridded state vector and perturbation scaling factor in HEMCO for IMI-GCC and IMI-GCHP To use gridded state vector and perturbation scaling factor in HEMCO for IMI Aug 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant