-
Notifications
You must be signed in to change notification settings - Fork 258
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
minor updates for FV3 "the dycore" and run templates, parm/field_table/* updated for RTS #870
Conversation
@bensonr would you please sync your ufs-weather-model branch with the latest develop branch and run RT on gaea? After that we will run RT on other platforms. Thanks |
Automated RT Failure Notification |
Not sure if this test timed out or not. It looks like the model ran to completion, but the post task was still doing something when the run aborted. Will recover the log file, rerun the failed tests and upload if successful. |
Automated RT Failure Notification |
I pushed the full regression test log for Cheyenne/GNU. |
Thanks, Dom
…On Mon, Oct 18, 2021 at 4:45 PM Dom Heinzeller ***@***.***> wrote:
/glade/scratch/dtcufsrt/autort/tests/auto/pr/759311817/20211018124512/ufs-weather-model
Not sure if this test timed out or not. It looks like the model ran to
completion, but the post task was still doing something when the run
aborted. Will recover the log file, rerun the failed tests and upload if
successful.
I pushed the full regression test log for Cheyenne/GNU.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#870 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AI7D6TKFESZQQAFPZJHOXZLUHSBNDANCNFSM5GCIBZOA>
.
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>.
|
jet was a time-out. I will rerun. |
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.
Nice cleanup work. I note the following:
- We should do the same with
diag_table
- use version-controller files from the ufs-weather-model repository for the regression tests - When a new input data set is created in future pull requests, remove all
field_table
(anddiag_table
if (1) has been completed by then) from the new input data set.
Automated RT Failure Notification |
…all chemistry tracers to zero for a cold start
What happened here? |
Gaea was a time out for that one test. I was going to re-run. |
gaea is "sick" and been experiencing performance issues. ORNL is planning to apply some fixes this week with the hope of addressing the Lustre issues that have been randomly plaguing the system for over two months. |
Time for gaea to get vaccinated ... |
…t to NOAA-EMC/fv3atm
fv3atm submodule pointer is correct, will merge. |
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.
Description
This PR brings in RTS updates from @junwang-noaa to fully use the FIELD_TABLE macro. In addition the field_tables in tests/parm/field_table/ have been modified to provide correct initialization values. Some of the run templates in tests/fv3_conf have been updated to reflect the FIELD_TABLE changes. FInally, minor bugfixes and updates for FV3 "the dycore" are included to coincide with the field_table updates.
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).
Do PRs in upstream repositories need to be merged first?
If so add the "waiting for other repos" label and list the upstream PRs