-
Notifications
You must be signed in to change notification settings - Fork 253
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
Update global GFS regression tests #561
Conversation
tests/parm/control_csawmg.nml.IN
Outdated
@@ -0,0 +1,303 @@ | |||
&amip_interp_nml |
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 namelist is not used. can be removed from all input.nml namelist templates
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.
@bensonr May I ask if the namelist amip_interp_nml variables are actually used in the FV3GFS runs?
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.
To my knowledge, this nml is unused.
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.
amip_interp is a deprecated method for providing amip datasets. It has been long superseded by the data_override capabilities which is much more powerful and used directly in many GFDL components and the FMS Coupling system. Please feel free to remove the nml references where needed.
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.
Rusty, thanks for the explanation. The amip_interp_nml is removed in the updated global tests.
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.
Shouldn't amip_interp_nml
be removed from all input_nml templates, not just global?
Rusty, |
OK, thanks. Should I re-run the gnu tests now that you've removed it from rt.conf? I will need to do some digging to resolve the CMEPS/gnu failure so that will take time. |
Yes, please add a note on the cheyenne gnu log file and commit the log file
as is. Thanks
…On Tue, Jun 1, 2021 at 1:47 PM Denise Worthen ***@***.***> wrote:
OK, thanks. Do you want me to commit the cheyenne gnu log as is? If so, I
will add a message about the failed gnu cpld test. I agree this will
require digging into the CMEPS code and should be made a separate issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#561 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AI7D6TJMXF6FPTMGDQDV3ULTQUML3ANCNFSM44IJPLPA>
.
|
* cpld tests should have been removed from rt.conf since testing on hera indicated they would fail. The failure is is in the Imp and Exp Accum counts in the mediator restart file. All other fields in the mediator restart file are identical.
*repeated test cpld_bmarkfrac_wave_v16_noahmp passed *no error in the log or run directory to explain the failed test the first time.
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.
A few comments, but nothing that should hold back the PR.
If I see this correctly, any remaining tests in tests/tests
starting with fv3_
I will need to work on in a follow-up PR?
|
||
COMPILE | APP=ATM SUITES=FV3_GFS_2017_fv3wam 32BIT=Y MULTI_GASES=Y DEBUG=Y | | fv3 | | ||
RUN | fv3_multigases_debug | | fv3 | | ||
#COMPILE | APP=ATM SUITES=FV3_GFS_2017_fv3wam 32BIT=Y MULTI_GASES=Y DEBUG=Y | | fv3 | |
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.
I just added this test, why is it commented out again?
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.
Because the multigases test requires FV3_GFS_2017_fv3wam suite file, which was not used in the new RT test suite any more. The fv3_multigases test was commented out. Henry/Kate is preparing a PR to update multigases test using new ICs from GFSv16 analysis file, they can update the fv3_multigases_debug test in their PR. This way we can get rid of the old GFSv14 ICs.
@@ -0,0 +1,40 @@ | |||
############################################################################### | |||
# | |||
# Global control csawmgt test |
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.
I am a little confused what the "control" stands for in all these tests. I thought control is GFS v16, and any suffix describes deviations from GFS v16 control (e.g. _flake, _2threads). But csawmg is an entirely different suite, for example.
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.
Yes, the control test is GFS_v16. Any suffix test has new updates from GFS_v16, it could be additional new features or new physics packages replacing current one used in opn GFS v16. In the case of csawmgt, the setting is based in L127 GFS_v16 test, only the related physics namelist are changed, the same for control_noahmp, control_rrtmgp, control_thompson, etc.
Bin Liu is updating the fv3_stretch tests, Henry/Kate on fv3_multigases. I think you will need to update other global tests including fv3_gsd, fv3_hafs and fv3_rrfs etc. |
utest changes to go with gfs_rt updates
…t out control_c384 tests due to reserved node limit on cray
…ity#561) * update upp, ccpp/physics and cmakelist to use w3emc 2.9.2
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
Provide a detailed description of what this PR does. What bug does it fix, or what feature does it add? Is a change of answers expected from this PR? Are any library updates included in this PR (modulefiles etc.)?
This is first incremental commit to update all the global tests.
This PR requires new input files for the GFSv16 tests.
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!)
#143
#528
#487
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).
fv3atm PR #321