GCClassic 14.1.1 Tagged CO HEMCO_config.rc GEOS_Chem.Restart files issues

[XunZhangNJU]

Name and Institution (Required)

Name: XunZhangNJU Institution: Nanjing University

Confirm you have reviewed the following documentation

• [x] Contributing guidelines

New HEMCO feature or discussion

Using GC 14.1.1 to do tagged CO simulation, time range: 20160701 - 20160801. Here are the 9 regions that I tagged,

In geomchem_config.yml transported_species: CO, CObbAS, CObbAUST, CObbNA, CObbNAE, CObbNHAF, CObbNHSA, CObbOTW (the rest of the world), CObbSEAS, CObbSHAF, CObbSHSA.

We have also modified HEMCO_Config.rc, HISTORY.rc, HEMCO_Diagn.rc, species_database.yml, which correspond with trasported species. When we compiled and running, a issue has occurred: HEMCO WARNING: Data is treated as unitless, but file attribute suggests it is not: mol mol-1 dry. File: ./Restarts/GEOSChem.Restart.20160701_0000z.nc4 --> LOCATION: HCOIO_READ (HCOIO_READ_STD_MOD.F90)

HEMCO ERROR: Cannot find field SPC_CObbAS. Please check variable name in the config. file

Then we converted SpeciesRst_?ALL? to SpeciesRst_CO, the error is fixed. ################### ###################

Here is my question: In the GEOSChem.Restart.20160701_0000z.nc4, cannot find field SPC_CObbAS, SPC_CObbAUST, SPC_CObbNA, SPC_CObbNAE, etc. Do we need to do spin-up to make the restrat file have these parameters? Or such this modification in HEMCO_Config.rc is not appropriate? If we need to do spin-up run, how long is appropriate? Thanks!

[yantosca]

Thanks for writing @XunZhangNJU. I believe the issue is that you need to change the EFYO time cycle flag to CYS because you have defined some new species that are not in the restart file. Also make sure that

See https://geos-chem.readthedocs.io/en/stable/gcc-guide/04-data/restart-files-gc.html and GEOS-Chem issues #1533 #1450 #1228, among others.

[stale[bot]]

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.

[stale[bot]]

Closing due to inactivity