-
Notifications
You must be signed in to change notification settings - Fork 250
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
brings in FV3 "the dycore" updated to be consistent with the latest public release #772
Conversation
* bypass control_csawmg test for gaea (numerical instability)
Rusty identified following dycore code updates will cause baselines to change:
|
@junwang-noaa - thanks for including the diff stats. Please be aware the new/modified code is denoted by a '-' and the original code is the '+' in the diff listed above. |
Machine: cheyenne |
Automated RT Failure Notification |
Weird. It says baseline creation was successful, and it looks like it was. For the verification step, I see the following error for the failing tests:
Not sure if this was a temporary issue, a disk space problem or what. Will try to run the verification step manually. |
On gaea, all the 4 failed tests were timed out. Will manually resubmit the
4 tests for baseline creation.
…On Thu, Aug 26, 2021 at 10:30 AM Brian Curtis ***@***.***> wrote:
*Automated RT Failure Notification*
Machine: gaea
Compiler: intel
Job: BL
Repo location:
/lustre/f2/pdata/ncep/emc.nemspara/autort/pr/720092158/20210826133005/ufs-weather-model
Please manually delete: /lustre/f2/scratch/emc.nemspara/FV3_RT/rt_26714
Test control_thompson_no_aero 030 failed failed
Test control_thompson_no_aero 030 failed in run_test failed
Test control_csawmgt 025 failed failed
Test control_csawmgt 025 failed in run_test failed
Test regional_quilt_hafs 035 failed failed
Test regional_quilt 034 failed failed
Test regional_quilt 034 failed in run_test failed
Test regional_quilt_hafs 035 failed in run_test failed
Test control_c384 016 failed failed
Test control_c384 016 failed in run_test failed
Please make changes and add the following label back:
gaea-intel-BL
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#772 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AI7D6TOCWOD2KD4FJCKQPMLT6ZFYXANCNFSM5C2HHSNQ>
.
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&utm_campaign=notification-email>
.
|
On gaea, all the 4 failed tests were timed out. Will manually resubmit the
4 tests for baseline creation.
… <#m_8415720038615092642_>
@bensonr <https://github.com/bensonr> Do we expect an increase in runtime
from the dycore update?
No I don't. I was able to run a full set of tests without fail on gaea and
both intel and gnu on hera last night.
|
Machine: cheyenne |
Automated RT Failure Notification |
Automated RT Failure Notification |
All tests that failed on gaea were timed out. For example, control_merra2 ran for 15 hours instead of 24 hours. I will manually re-run those 3 tests. |
Thanks, Minsuk.
…On Thu, Aug 26, 2021 at 2:15 PM Minsuk Ji ***@***.***> wrote:
All tests that failed on gaea were timed out. For example, control_merra2
has ran for 15 hours instead of 24 hours. I will manually re-run those 3
tests.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#772 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AI7D6TNKPQW7PQGIVQAI3YTT62ADRANCNFSM5C2HHSNQ>
.
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&utm_campaign=notification-email>
.
|
@BrianCurtis-NOAA The orion baseline was created successfully, but the baseline was not copied to the /work/noaa/nems/emc.nemspara/RT/NEMSfv3gfs/develop-20210825/INTEL, would you please manually copy them, then change permission so that all the developers can see it? Thanks |
Sure thing. I've started the rsync. Once completed I'll add the orion intel RT label. |
@bensonr the wcoss dell/cray log files are on hera at:
Please commit them to your branch |
@junwang-noaa - wcoss regression logs are in place |
Automated RT Failure Notification |
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.
Approved contingent on jet.intel tests passing (and the usual submodule/.gitmodules procedure).
With current Jet issues, you may want to skip it for this PR. |
I have jet log file ready, but now jet is not accessible. Will attach to the PR when jet is back. |
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.
If new or updated input data is required by this PR, it is clearly stated in the text of the PR.
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 brings in an update for fv3atm that contains updates to the latest public release of the FV3 dycore encapsulated in PR #128.
This PR also disables the control_csawmg test for gaea.intel due to a numerical instability brought about by the updates to the dycore. The same test runs to completion on hera.intel.
This PR requires a new datestamp for the RTS ICs. The particular updates are to the gdas tests which pass regression test for this update.
This PR changes answers for all regional tests and any test with ICs created by chgres from sources that sets the data_source_fv3gfs=.true. option in FV3/atmos_cubed_sphere/tools/external_ic.F90::get_nggps_ic routine. Therefore new baselines will need to be created.
Issue(s) addressed
Link the issues to be closed with this PR, whether in this repository, or in another repository.
(Remember, issues must always be created before starting work on a PR branch!)
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
If testing this branch requires non-default branches in other repositories, list them. Those branches should have matching names (ideally).
bensonr/GFDL_atmos_cubed_sphere/tree/master2emc
bensonr/fv3atm/tree/dycore
Do PRs in upstream repositories need to be merged first?
If so add the "waiting for other repos" label and list the upstream PRs