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
Name: Lizzie Lundgren
Institution: Harvard University
New GCClassic feature or discussion
I am testing a new meteorology source in GC-Classic. In order to do this I need to change code in HEMCO and GEOS-Chem repositories and recompile. This is in addition to changing settings in geoschem_config.yml, HEMCO_Config.rc, and HEMCO_Config.rc.gmao_metfields, some of which are redundant. This is much more complicated than in GCHP which simply requires changing paths in ExtData.rc and rerunning.
I suggest that we take a look at how we handle meteorology inputs in GEOS-Chem Classic to see if we can make it a run-time option and with more flexibility and simplicity. I'll think about how to do this in preparation for adding GEOS-IT as a standard option in the model.
The text was updated successfully, but these errors were encountered:
Name and Institution (Required)
Name: Lizzie Lundgren
Institution: Harvard University
New GCClassic feature or discussion
I am testing a new meteorology source in GC-Classic. In order to do this I need to change code in
HEMCO
andGEOS-Chem
repositories and recompile. This is in addition to changing settings ingeoschem_config.yml
,HEMCO_Config.rc
, andHEMCO_Config.rc.gmao_metfields
, some of which are redundant. This is much more complicated than in GCHP which simply requires changing paths inExtData.rc
and rerunning.I suggest that we take a look at how we handle meteorology inputs in GEOS-Chem Classic to see if we can make it a run-time option and with more flexibility and simplicity. I'll think about how to do this in preparation for adding GEOS-IT as a standard option in the model.
The text was updated successfully, but these errors were encountered: