Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FEATURE REQUEST] Make adding/changing meterology source a run-time option #40

Open
lizziel opened this issue Jun 15, 2023 · 0 comments
Assignees
Labels
category: Feature Request New feature or request

Comments

@lizziel
Copy link
Contributor

lizziel commented Jun 15, 2023

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 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.

@lizziel lizziel self-assigned this Jun 15, 2023
@lizziel lizziel added the category: Feature Request New feature or request label Jun 15, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category: Feature Request New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant