geoschem / HEMCO

The Harmonized Emissions Component (HEMCO), developed by the GEOS-Chem Support Team.
https://hemco.readthedocs.io
Other
17 stars 32 forks source link

[BUG/ISSUE] Offline emissions are not updated at the correct frequency #184

Open viral211 opened 1 year ago

viral211 commented 1 year ago

I am running HEMCO with GEOS-Chem classic version 14.0 and am using offline emissions for dust, sea salt, etc. I noticed that the emissions are not updated at the right frequency. For example, the offline dust emission settings in the default FullChem HEMCO_Config.rc file are as follows:

#==============================================================================
# --- Offline dust emissions ---
#==============================================================================
(((OFFLINE_DUST
(((.not.DustDead.or.DustGinoux
0 EMIS_DST1 $ROOT/OFFLINE_DUST/v2021-08/${RUNDIR_MET_NATIVE_RES}/$YYYY/$MM/dust_emissions_${RUNDIR_MET_LAT_RES}.$YYYY$MM$DD.nc EMIS_DST1 1980-2022/1-12/1-31/* EF xy kg/m2/s DST1 - 3 2

The dust emissions emissions should be updated daily, but instead they are read in just once at the beginning of the simulation. This applies to sea salt aerosols, soil NOx and biogenic VOC emissions also. I can get this to work correctly when I change the cycle flag from 'EF' to 'C', which was the flag used in previous model versions. I think the problem might be here: https://github.com/geoschem/HEMCO/blob/344429fbe2ac9b4f1262aa03a95bf3cad5dd02e0/src/Core/hcoio_read_std_mod.F90#L256-L277

yantosca commented 1 year ago

Thanks @viral211, we'll take a look. Also tagging @msulprizio @Jourdan-He @SaptSinha @jimmielin

stale[bot] commented 1 year ago

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.

msulprizio commented 1 year ago

Sorry for the late reply @viral211. We fixed this issue in 14.1.0 (in the benchmark review stages now). See https://github.com/geoschem/geos-chem/issues/1321 and the fix at https://github.com/geoschem/geos-chem/pull/1595.