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

[viral211]

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:

HEMCO/src/Core/hcoio_read_std_mod.F90

Lines 256 to 277 in 344429f

	! If the file has cycle flag "E" (e.g. it's a restart file), then we will
	! read it only once and then never again. If the file has already been
	! read on a previous call, then don't call HCOIO_READ. (bmy, 10/4/18)
	!
	! Moved this handling from hcoio_dataread_mod, as it is non-MAPL specific
	! (hplin, 4/5/21)
	IF ( Lct%Dct%Dta%CycleFlag == HCO_CFLAG_EXACT .and. &
	Lct%Dct%Dta%UpdtFlag == HCO_UFLAG_ONCE .and. &
	Lct%Dct%Dta%isTouched ) THEN
	! Print a warning message only once
	IF ( doPrintWarning ) THEN
	doPrintWarning = .FALSE.
	MSG = 'No further attempts will be made to read file: ' // &
	TRIM( Lct%Dct%Dta%NcFile )
	CALL HCO_WARNING ( HcoState%Config%Err, MSG, RC, WARNLEV=1 )
	ENDIF
	! Return without reading
	CALL HCO_LEAVE( HcoState%Config%Err, RC )
	RETURN
	ENDIF

[yantosca]

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

[stale]

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]

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