Add tagged O3 run directory for GCHP #1167
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Thanks @xpye98! This looks good to me. There are some changes in createRunDir.sh that are going into 13.4.0 which cause conflicts, but we can take care of those. |
lizziel
added
category: Feature Request
|
This PR still uses the input.geos file. In 13.4.1, that file was replaced with geoschem_config.rc. Before accepting and merging this PR, that change should be made here. |
|
The input.geos file has been moved under geoschem_config.yml.templates. New PR #1380 has been created. |
|
This PR is now superseded by #1380. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi, all,
I recently put together a tagged O3 run directory for GCHP. Thanks to the good compatibility of GCC and GCHP, it only involves some changes and addition of configuration files. I have tested the code and run tagO3 simulation for several days , and the result seems to be similar to GCC's.
One thing I also did is to create a directory,
ExtData/HEMCO/GCHP_Output/13.0.0/, to archive my daily prod/loss rates from fullchem simulation (just like the path in GCC tagO3). I think we can generate this directory and put some default prod/loss rates there for users to test.geoschem/GCHP#201