geoschem / geos-chem

GEOS-Chem "Science Codebase" repository. Contains GEOS-Chem science routines, run directory generation scripts, and interface code. This repository is used as a submodule within the GCClassic and GCHP wrappers, as well as in other modeling contexts (external ESMs).
http://geos-chem.org
Other
170 stars 165 forks source link

How to use climatological met data (using 1 year for multi-year) #2465

Open aschuh opened 2 months ago

aschuh commented 2 months ago

Your name

Andrew Schuh

Your affiliation

Colorado State University

Please provide a clear and concise description of your question or discussion topic.

If I want to use 1 year of met driving data, is it just replacing the default EFY with C in ALL the following met lines of HEMCO?

# --- A1 fields ---
* ALBEDO    $METDIR/$YYYY/$MM/$MET.$YYYY$MM$DD.A1.$RES.$NC     ALBEDO   1900-2100/1-12/1-31/*/+30minute EFY xy  1  * -  1 1
* CLDTOT    $METDIR/$YYYY/$MM/$MET.$YYYY$MM$DD.A1.$RES.$NC     CLDTOT   1900-2100/1-12/1-31/*/+30minute EFY xy  1  * -  1 1
msulprizio commented 1 month ago

Hi @aschuh. Yes, you can change EFY to C to use the closest available date. However, note that HEMCO will choose the closest date according to the data available on your system so if you have other years available if may not stick to the single year as you expect. To force the correct behavior, you should be able to instead change the $YYYY token in the met field entries to the year of your choice and HEMCO will only look for files for that year.

Note: HEMCO does have the option of specifying Emissions year in the config file which will hardcode the year of emissions for all inventories, but the same option doesn't exist yet for simulation year. We could consider adding a feature request for this if it would benefit the community. I think this could be done by modifying these lines in hco_clock_mod.F90.

github-actions[bot] commented 5 days 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 issue from closing this issue.