You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GCHP user @clearsky112 reported in geoschem/GCHP#127 the following error in the primary GCHP log file when running. No HEMCO.log file was generated making it difficult to determine the problem.
Error in HcoDiagn_Init called from HCO_Init
===============================================================================
GEOS-Chem ERROR: Error encountered in "HCO_Init"!
-> at HCOI_GC_Init (in module GeosCore/hco_interface_gc_mod.F90)
THIS ERROR ORIGINATED IN HEMCO! Please check the HEMCO log file for
additional error messages!
===============================================================================
===============================================================================
GEOS-Chem ERROR: Error encountered in "HCOI_GC_Init"!
-> at Emissions_Init (in module GeosCore/emissions_mod.F90)
===============================================================================
pe=00003 FAIL at line=00257 gchp_chunk_mod.F90 <Error calling EMISSIONS_INIT>
pe=00003 FAIL at line=02022 Chem_GridCompMod.F90 <status=1>
pe=00003 FAIL at line=01829 MAPL_Generic.F90 <needs informative message>
pe=00003 FAIL at line=01484 MAPL_Generic.F90 <needs informative message>
pe=00003 FAIL at line=00279 GCHP_GridCompMod.F90 <status=1>
pe=00003 FAIL at line=01829 MAPL_Generic.F90 <needs informative message>
pe=00003 FAIL at line=00556 MAPL_CapGridComp.F90 <status=1>
pe=00003 FAIL at line=00849 MAPL_CapGridComp.F90 <status=1>
pe=00003 FAIL at line=00322 MAPL_Cap.F90 <status=1>
pe=00003 FAIL at line=00198 MAPL_Cap.F90 <status=1>
pe=00003 FAIL at line=00157 MAPL_Cap.F90 <status=1>
pe=00003 FAIL at line=00131 MAPL_Cap.F90 <status=1>
pe=00003 FAIL at line=00029 GCHPctm.F90 <status=1>
The user figured out they could output the HEMCO.log file by changing the HEMCO_Config.rc setting for DiagnFreq from Monthly to End. This was presumably an issue because the test run was 1-hour, less than the 1-month frequency set for that field. After making this change, the HEMCO.log file was output successfully and contained error messages indicating the underlying problem, specifically that input files that were missing.
This is unexpected behavior for GCHP since we previously thought the DiagnFreq field was ignored. Diagnostic frequency is set in HISTORY.rc instead. However, it seems this field has an impact on creation of the HEMCO.log file. We should further investigate this so that it is a not a problem in future versions.
The text was updated successfully, but these errors were encountered:
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.
GCHP user @clearsky112 reported in geoschem/GCHP#127 the following error in the primary GCHP log file when running. No
HEMCO.log
file was generated making it difficult to determine the problem.The user figured out they could output the
HEMCO.log
file by changing theHEMCO_Config.rc
setting forDiagnFreq
fromMonthly
toEnd
. This was presumably an issue because the test run was 1-hour, less than the 1-month frequency set for that field. After making this change, theHEMCO.log
file was output successfully and contained error messages indicating the underlying problem, specifically that input files that were missing.This is unexpected behavior for GCHP since we previously thought the
DiagnFreq
field was ignored. Diagnostic frequency is set inHISTORY.rc
instead. However, it seems this field has an impact on creation of theHEMCO.log
file. We should further investigate this so that it is a not a problem in future versions.The text was updated successfully, but these errors were encountered: