-
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
Attribute cleanup, allow coupled executable to run as standalone; update WW3 to use CPP instead of switches (was #880) #868
Attribute cleanup, allow coupled executable to run as standalone; update WW3 to use CPP instead of switches (was #880) #868
Conversation
Automated RT Failure Notification |
Jet failure for the cdeps test was
The compile_012 error was a long string of messages like
I'll re-run the affected tests. |
I got the same message on jet again with the slurm/sacct error. |
Let me try it on jet. I don't think there is any change related to the stochastic physics though. |
I think it must be some system issue. Didn't Bin have trouble yesterday? |
No. We had 4 tests not finishing by the wall clock time, but there was no
issue compiling the code.
…On Tue, Nov 2, 2021 at 4:32 PM Denise Worthen ***@***.***> wrote:
I think it must be some system issue. Didn't Bin have trouble yesterday?
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
<#868 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AI7D6TLCC2ZDWE3Q2O6625LUKBKE7ANCNFSM5GBTGYJQ>
.
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 submitted the three tests serially (no -e) and the compile 012 job ( |
I reran the failed case on jet, it finished successfully. |
@aliabdolali @JessicaMeixner-NOAA Ready to merge to ufs-weather-model once WW3 has been updated. |
@DeniseWorthen, @aliabdolali just approved and merged the WW3 PR |
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
Updates NEMS to allow the coupled executable to run as the standalone (i.e.,
app=S2S
run asapp=ATM
).Issue(s) addressed
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)
The full RTs were run for hera.intel, hera.gnu and cheyenne.intel. All baselines were B4B.
A second test was done on cheyenne.intel using the following rt.conf:
After the test completed, the coupled executable was copied into the
control_p7
run directory and the test was re-run using the job_card. The forecast and restart files from this second run ofcontrol_p7
were B4B with the run using the original standalone executable.Dependencies
If testing this branch requires non-default branches in other repositories, list them. Those branches should have matching names (ideally).