adding hr_ave_chem_v1#1513
Conversation
|
@JianpingHuang-NOAA can you sync up branch and resolve the conflict? we can start working on this pr. |
|
I see crashing erros on cheyenne. intel: 0:FATAL from PE 0: Missing hourly-averaged o3 or pm25 in diag_table |
@JianpingHuang-NOAA what changes to field table or config files do I need to make? |
|
Please add the following 4 lines in the diag_table_aqm.FV3_GFS_v16 if you
use ccpp=FV3_GFS_v16 or diag_table_aqm.FV3_GFS_v15p2 if you use
ccpp=FV3_GFS_v15p2
"gfs_dyn", "o3_ave", "o3_ave", "fv3_history", "all",
.false., "none", 2
"gfs_dyn", "no_ave", "no_ave", "fv3_history", "all",
.false., "none", 2
"gfs_dyn", "no2_ave", "no2_ave", "fv3_history", "all",
.false., "none", 2
"gfs_dyn", "pm25_ave", "pm25_ave", "fv3_history", "all",
.false., "none", 2
…On Mon, Dec 5, 2022 at 3:47 PM JONG KIM ***@***.***> wrote:
I see crashing erros on cheyenne. intel: 0:FATAL from PE 0: Missing
hourly-averaged o3 or pm25 in diag_table
—
Reply to this email directly, view it on GitHub
<#1513 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANA2PI5S7K62XX7T7T2P5BDWLZIEBANCNFSM6AAAAAASRIFOVY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Sounds like output files change as diag table changes. Comparing atmf000.nc ............ALT CHECK......NOT OK I am adding baseline change labels. |
|
With this update, total PM2.5 is computed within the AQM. It is not
necessary to output all PM species and related parameters for PM2.5
calculation through UPP. In the final diag table, we propose to reduce the
number of 3-D variables and tracers from more than 190 to 11 to support the
AQM v7 implementation.
…On Mon, Dec 5, 2022 at 5:59 PM JONG KIM ***@***.***> wrote:
Sounds like output files change as diag table changes. Comparing
atmf000.nc ............ALT CHECK......NOT OK I am adding baseline change
labels.
—
Reply to this email directly, view it on GitHub
<#1513 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ANA2PIZF2X7SQPUF6VUDPRTWLZXTRANCNFSM6AAAAAASRIFOVY>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
Automated RT Failure Notification |
|
Automated RT Failure Notification |
|
Automated RT Failure Notification |
|
Automated RT Failure Notification |
|
OK. Looks like baselines change across the board. |
|
all these failures complains same error: Missing hourly-averaged o3 or pm25 in diag_table |
|
OK. I testing on Orion with a control test and atmaq test and both passed with the changes made in atmos_cubed_sphere in FV3. Should be able to run AutoRT now (no baselines needed past atmaq tests) |
on-behalf-of @ufs-community <brian.curtis@noaa.gov>
on-behalf-of @ufs-community <brian.curtis@noaa.gov>
|
Automated RT Failure Notification |
on-behalf-of @ufs-community <brian.curtis@noaa.gov>
on-behalf-of @ufs-community <brian.curtis@noaa.gov>
|
Gaea/c4 slowness on Dec 06 + fixed mis-handled baselines. Anyway, all tests are done even including hera. We can start merging process. Dependencies first. I will ask to merge in the cubed_sphere pr first. |
4 participants
PR Checklist
This PR is up-to-date with the top of all sub-component repositories except for those sub-components which are the subject of this PR. Please consult the ufs-weather-model wiki if you are unsure how to do this.
This PR has been tested using a branch which is up-to-date with the top of all sub-component repositories except for those sub-components which are the subject of this PR
An Issue describing the work contained in this PR has been created either in the subcomponent(s) or in the ufs-weather-model. The Issue should be created in the repository that is most relevant to the changes in contained in the PR. The Issue and the dependent sub-component PR
are specified below.
Results for one or more of the regression tests change and the reasons for the changes are understood and explained below.
New or updated input data is required by this PR. If checked, please work with the code managers to update input data sets on all platforms.
Instructions: All subsequent sections of text should be filled in as appropriate.
The information provided below allows the code managers to understand the changes relevant to this PR, whether those changes are in the ufs-weather-model repository or in a subcomponent repository. Ufs-weather-model code managers will use the information provided to add any applicable labels, assign reviewers and place it in the Commit Queue. Once the PR is in the Commit Queue, it is the PR owner's responsibility to keep the PR up-to-date with the develop branch of ufs-weather-model.
Description
Update the online-calculation and writing of hourly-averaged fields for chemical species for O3, NO, NO2, and PM2.5
Testing
How were these changes tested? What compilers / HPCs was it tested with? Are the changes covered by regression tests? (If not, why? Do new tests need to be added?) Have regression tests and unit tests (utests) been run? On which platforms and with which compilers? (Note that unit tests can only be run on tier-1 platforms)
Dependencies
Do PRs in upstream repositories need to be merged first?
If so add the "waiting for other repos" label and list the upstream PRs
NOAA-EMC/ufsatm#608
NOAA-GFDL/GFDL_atmos_cubed_sphere#226