Skip to content
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

Merged
merged 80 commits into from
Jun 2, 2021

Conversation

junwang-noaa
Copy link
Collaborator

@junwang-noaa junwang-noaa commented May 7, 2021

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.

  • Most GFSv14/GFSv15 based tests are updated to GFSv16 confiscation, the cold start ICs were created from GFSv16 anaylysis. A GDAS forecast case using IAU is also setup.
  • Debug tests are added for global regression tests
  • History file names are changed from "phyf/dynf" to operational file names "sfcf/atmf"
  • Restart files for baseline comparison are removed from the GFSv16 feature tests, only those tests with restart will still have restart files comparison
  • There is no change in non-GFS configuration tests using gsd, rrtf, hafs physics package
  • The first commit has no changes in cpld tests and datm tests.
  • The inline post issue in post interface post_*.F90 is fixed for gnu compiler.
  • amip_interp_nml namelist is removed from all the name list files
  • Unused configuration varaibles: cpl, memuse_verbose, atmos_nthreads, use_hyper_thread, ncores_per_node are removed from model_configure
  • Input data directory input-data-20210528 has new 172 leves 2021032206 ICs for C96, C192 and C384 global input files.

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!)

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)

  • hera.intel
  • hera.gnu
  • orion.intel
  • cheyenne.intel
  • cheyenne.gnu
  • gaea.intel
  • jet.intel
  • wcoss_cray
  • wcoss_dell_p3

Dependencies

If testing this branch requires non-default branches in other repositories, list them. Those branches should have matching names (ideally).

fv3atm PR #321

@junwang-noaa junwang-noaa changed the title Gfs rt Update global GFS regression tests May 7, 2021
@@ -0,0 +1,303 @@
&amip_interp_nml
Copy link
Collaborator

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

Copy link
Collaborator Author

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?

Copy link
Contributor

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.

Copy link
Contributor

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.

Copy link
Collaborator Author

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.

Copy link
Collaborator

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?

@yangfanglin
Copy link
Collaborator

Rusty,
I'd suggest we keep it in case developers want to run AMIP-type experiments, although I do not know if this is specifically set up for AMIP experiments. Has GFDL ever used this option ?

@DeniseWorthen
Copy link
Collaborator

DeniseWorthen commented Jun 1, 2021

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.

@junwang-noaa
Copy link
Collaborator Author

junwang-noaa commented Jun 1, 2021 via email

DeniseWorthen and others added 3 commits June 1, 2021 11:58
* 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.
DeniseWorthen and others added 3 commits June 1, 2021 12:41
*repeated test cpld_bmarkfrac_wave_v16_noahmp passed
*no error in the log or run directory to explain
the failed test the first time.
Copy link
Collaborator

@climbfuji climbfuji left a 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 |
Copy link
Collaborator

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?

Copy link
Collaborator Author

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
Copy link
Collaborator

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.

Copy link
Collaborator Author

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.

@junwang-noaa
Copy link
Collaborator Author

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?

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
@junwang-noaa junwang-noaa merged commit b474679 into ufs-community:develop Jun 2, 2021
@junwang-noaa junwang-noaa deleted the gfs_rt branch November 24, 2021 14:51
@junwang-noaa junwang-noaa mentioned this pull request Dec 7, 2021
16 tasks
pjpegion pushed a commit to NOAA-PSL/ufs-weather-model that referenced this pull request Apr 4, 2023
…ity#561)

* update upp, ccpp/physics and cmakelist to use w3emc 2.9.2
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Baseline Updates Current baselines will be updated. New Input Data Req'd This PR requires new data to be sync across platforms Waiting for Reviews The PR is waiting for reviews from associated component PR's.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Large MERRA2 climatology files copied for many regression tests, even though they are not neeeded
9 participants