-
Notifications
You must be signed in to change notification settings - Fork 251
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
Add GP ORTs #946
Add GP ORTs #946
Conversation
Please update to the last commit for FV3 and ufs-weather. |
@DeniseWorthen |
tests/tests/control_p7_rrtmgp
Outdated
|
||
export FV3_RUN=control_run.IN | ||
export CCPP_SUITE=FV3_GFS_v16_p7_rrtmgp | ||
export NEW_DIAGTABLE=diag_table_gfsv16_merra2 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This needs to be consistent with the newest control_p7 test (NEW_DIAGTABLE-> DIAGTABLE)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done.
Could you update your PR information for the CCPP-physics PR? It is showing as closed. Also, is there an issue in either FV3 or CCPP that you can list in the 'issues addressed' section? |
@DeniseWorthen |
I am not able to build
|
@MinsukJi-NOAA |
@dustinswales Could you grab the ORT results for |
@MinsukJi-NOAA |
Please update |
When I run this through allinea ddt, I get weird values for gptS, see attached screenshot. |
@DomHeinzeller That is certainly an error. It suggests corrupted memory, I guess. |
@DomHeinzeller is |
…mg_debug on Jet w/ Intel
We don't have this compiler flag yet, will try manually. This is the screenshot for exactly the same run, same place, when compiled in DEBUG mode. The values look good. |
@dustinswales would you please merge Dom's PR to update the rt.conf? Thanks. |
Turn off tests in rt.conf
@dustinswales I have a little more info. The repro mode is apparently broken due to previous build system updates (recall that we don't really test the repro mode ... a flaw). I run in prod mode, I get more information on the variables. I stopped the model in DDT before the offending line. The screenshot shows that jeta(2) has one bogus (for reasons I do not know yet). Also look at variables fmajor and k ... |
@DomHeinzeller @dustinswales Variable |
This probably happens because something else is writing into the variables ... I guess
… On Dec 8, 2021, at 10:22 AM, Robert Pincus ***@***.***> wrote:
@DomHeinzeller <https://github.com/DomHeinzeller> @dustinswales <https://github.com/dustinswales> Variable jeta is set on line 104 of the same file. Tracing up you can see there should be no way to get a negative value. I don't know what to make of the debugger not being able to read fmajor
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub <#946 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AN7FF5AA4BM4SAUQ6OPB2Q3UP6H57ANCNFSM5JPEPSQQ>.
Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.
|
I guess too, but who? And why would someone do such a thing 😢 |
@DomHeinzeller In more seriousness, these variables are all internal to RRTMGP. The big tables like |
Automated RT Failure Notification |
@dustinswales Logs are not being posted from any of the RTs because they can't get pushed to your fork. I'll collect them in once place for you to commit. The cheyenne.intel baseline created but I think I'm not sure the verify ran or where it is located. I may just run it manually if I can't find it. |
The jet.intel failure of the |
@dustinswales Please commit the logs in /scratch2/NCEPDEV/stmp1/Denise.Worthen/PR946 |
I am getting build error on my laptop when compiling mo_gas_optics_kernel:
in CMakeLists.txt I see two
Could this be the reason for the crash on Cheyenne. |
Definitely, this could be the problem. Need to figure out why this happens. Thanks for pointing this out! |
Attention
This PR was merged with the wrong fv3atm submodule pointer hash. The hash referenced in this branch (cf0a73180b2d9ac55ebfce4785a7270d205423db) resides/d in @dustinswales's fv3atm fork. The correct fv3atm hash in the NOAA-EMC repository would have been 86d4bb3.
PR Checklist
Ths 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 responsiblity to keep the PR up-to-date with the develop branch of ufs-weather-model.
Description
This PR contains new operational regression tests for RRTMGP in physics prototype 7.
Issue(s) addressed
See NCAR/ccpp-physics#782 for description of issues.
Testing
Testing at commit b707db5 on Cheyenne against baseline
develop-20211203
shows the following:GNU: all jobs ran to completion. The following two tests failed comparison (as expected):
INTEL: All non-RRTMGP tests ran to completion and passed. The following test ran to completion but failed comparison (as expected):
The following jobs compiled but failed at runtime:
These were tested on Intel and gnu on Hera.
This PR contains new tests to be added to tests/rt.conf.
Dependencies