-
Notifications
You must be signed in to change notification settings - Fork 155
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
Adding ProdLoss Rate of O3 to KPP #2337
Comments
Thanks for writing @yangning-code and thanks for your patience. Many of us were at the IGC11 meeting earlier and June. A few people have reported similar issues with the prod/loss diagnostic. We will be looking into this soon. Stay tuned. |
@yangning-code: From this error message: GEOS-Chem ERROR: Could not locate Prod_PO3 diagnostics state registry. it looks like the model is looking for a |
I noted that you used KPP v2.3.3. There have been many updates since then. Please try again with KPP 3.1.1 (the current version) and let me know if you still get the same error. |
Your name
Ning Yang
Your affiliation
JNU
Please provide a clear and concise description of your question or discussion topic.
GEOS-Chem version: v13.3.2
I wish to add the Production and loss rates of O3 to ProdLoss collection. However, after following below procedure , I do not see Prod_O3 nor Loss_O3 in my ProdLoss output files.
My implementation:
First, I added the following to fullchem.kpp file:
Then I recompiled the KPP using v2.3.3 running lines like:
After recompiling the KPP, I saw that PO3 and LO3 appearing on gckpp_Monitor.F90,gckpp_Parameters.F90, gckpp.kpp, gckpp.log, and fullchem.kpp files. This is consistent with our families that are defined in fullchem.kpp.
Then in my run directory, I modified the species_database.yml file so that it includes definition of PO3 and LO3:
After recompile my build directory, on my HISTORY.rc, I collect the ProdLoss COLLECTION such as Prod_O3 and Loss_O3.
When I collect Prod_O3 and Loss_O3 in HISTORY.rc ProdLoss Collection, I get the following error:
However,I also tried Prod_CO and Loss_CO Prod_?PRD? and Loss_?LOS? in HISTORY.rc ProdLoss Collection, The mode can run normally and can output PO3, LO3, PCO, LCO.
The text was updated successfully, but these errors were encountered: