Closed wreckdump closed 3 years ago
Thanks for writing @wreckdump. I think the issue is this:
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
% Chemistry is set to false in input.geos so chemistry %
% data will not be read by HEMCO (hcoi_gc_main_mod.F90) %
%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%
This code (in GeosCore/hco_gc_interface_mod.F90) turns off the chemistry data input via HEMCO if chemistry is turned off in input.geos:
!-----------------------------------------------------------------------
! If chemistry is turned off, do not read chemistry input data
!-----------------------------------------------------------------------
IF ( .NOT. Input_Opt%LCHEM ) THEN
IF ( Input_Opt%amIRoot ) THEN
Print*, '%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%'
Print*, '% Chemistry is set to false in input.geos so chemistry %'
Print*, '% data will not be read by HEMCO (hco_interface_gc_mod.F90)%'
Print*, '%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%'
ENDIF
OptName = 'CHEMISTRY_INPUT : false'
CALL AddExtOpt( HcoConfig, TRIM(OptName), CoreNr, RC=HMRC )
! Trap potential errors
IF ( HMRC /= HCO_SUCCESS ) THEN
RC = HMRC
ErrMsg = 'Error encountered in "AddExtOpt( CHEMISTRY_INPUT )"!'
CALL GC_Error( ErrMsg, RC, ThisLoc, Instr )
RETURN
ENDIF
ENDIF
but it should not turn off the metorology input. Take a look at your HEMCO_Config.rc file and make that the METEOROLOGY
switch is always turned on:
# ----- MASTER SWITCHES ---------------------
--> EMISSIONS : true
--> METEOROLOGY : true
--> CHEMISTRY_INPUT : true
if not, then HEMCO won't read in the meteorology data.
Yup. That was the problem! Thank you!
Report a GEOS-Chem bug or technical issue
Describe the bug:
Expected behavior:
I expected the model to run. I did download the ExtData/GEOS_4x5/MERRA2/2015/01/MERRA2.20150101.CN.4x5.nc4 file into the data directory, but the model can not read it somehow. The file is not corrupted, I did confirm it with ncdump/ncview. I even tried to change the file name to MERRA2.20160101.CN.4x5.nc4 and move it to the 2016/01 directory, but it gave me the same error messages.
Actual behavior:
It wouldn't run with the error message shown below.
Steps to reproduce: the bug:
Run commands
Error messages
Required information:
Your GEOS-Chem version and runtime environment:
Input and log files to attach
Additional context