-
Notifications
You must be signed in to change notification settings - Fork 172
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
SpeciesConcSubset is not working in the HISTORY.rc #2217
Comments
Thanks for writing @jinlx. Try adding the LON_RANGE and LAT_RANGE before the fields tag. Anything that comes after fields is assumed to be a diagnostic field name. |
@jinlx: I know that a lot of History documentation is still left on the wiki. We need to port them over to ReadTheDocs eventually but haven't gotten around to it yet due to other priorities. |
@yantosca, I think we could add the lat and lon ranges to this list in diaglist_mod.F90 to avoid the error too. Maybe excluding them was an omission since they were added later. geos-chem/Headers/diaglist_mod.F90 Lines 639 to 647 in b288af1
|
Good point @lizziel. |
This PR merges the most recent commits as of PR #2217 back into the bugfix/carbon-gchp-extdata branch. This is necessary as there were some additional fixes for the carbon simulation in PR #2266. Signed-off-by: Bob Yantosca <[email protected]>
Name and Institution (Required)
Name: Lixu Jin
Institution: University of Montana
Description of your issue or question
I was trying to use GC14.2.3 to save out subset from HISTORY.rc. However, setting up LON_RANGE and LAT_RANGE might be conflicted with error checking in ./Headers/diaglist_mod.F90.
Thus, I further commented the error check and try to walk around the error. However, this further results in a error said the SPECIESCONCSUBSET.LON_RANGE:-114.0-113.0 is not found in the registry for the DIAG object. I was wondering if there is any easy fix to make the SPECIESCONCSUBSET work in the recent GC version. Thanks!
To repeat the issue, you need to set up a SpeciesConcSubset. Below goes an template I used in the HISTORY.rc
The text was updated successfully, but these errors were encountered: