fixes for coupled model P7 restart tests and Update build system and regression testing on Acorn (PR#809) #819
Conversation
junwang-noaa
changed the title
junwang-noaa
requested review from
DeniseWorthen,
climbfuji and
DusanJovic-NOAA
junwang-noaa
added
No Baseline Change
|
@junwang-noaa please bring these up to date with respective authoritative repositories
|
1 similar comment
|
@junwang-noaa please bring these up to date with respective authoritative repositories
|
The error message from cpld_control_wave, the job did not start, will rerun this job
|
junwang-noaa
changed the title
|
Yay, gaea is back like in the good old days. The runtimes are reasonable again. |
| from __future__ import print_function | ||
| import ecflow | ||
| import ecflow as ecflow |
There was a problem hiding this comment.
I was getting some errors on Acorn, maybe something was wrong with ecflow installation. They keep changing things, I'll test again and remove it if it's not necessary anymore.
There was a problem hiding this comment.
Looks like they installed the latest version of ecflow the same day, or day before I made this change:
$ ls -dl /apps/ops/prod/nco/core/ecflow.v5.6.0.*
drwxr-xr-x 8 ops.prod prod 87 Apr 14 00:08 /apps/ops/prod/nco/core/ecflow.v5.6.0.3
drwxr-xr-x 8 ops.prod prod 87 Aug 5 16:15 /apps/ops/prod/nco/core/ecflow.v5.6.0.4
drwxr-xr-x 8 ops.prod prod 87 Aug 17 15:39 /apps/ops/prod/nco/core/ecflow.v5.6.0.5
drwxr-xr-x 8 ops.prod prod 87 Sep 2 19:58 /apps/ops/prod/nco/core/ecflow.v5.6.0.6
Who knows what the differences are between 5.6.0.5 and 5.6.0.6.
…or stochastic physics. (#819) * Add path_to_defns argument to set_FV3nml_ens_stoch_seeds. * Keep hour in directory name of ensemble members. * Fix SPP/T flag * Fix indentation of error/info message containing settings * Bugfix for DO_SHUM/SKEB which came from shell workflow generation * Fix nam_spp/p/erts confusion. * Make create_diag_table info/error message more informative. * Minor fix in info message. * Add a WE2E test case for testing stochastic physics. * Modify stoch phys test case.
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 contains the NoahMP and CA fixes for coupled tests restart reproducibility. It also adds a standalone FV3 P7 CCPP suite file. It does not change the current regression test results.
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).