Skip to content

Update CMEPS#1444

Closed
DeniseWorthen wants to merge 7 commits into
ufs-community:developfrom
DeniseWorthen:feature/updcmeps
Closed

Update CMEPS#1444
DeniseWorthen wants to merge 7 commits into
ufs-community:developfrom
DeniseWorthen:feature/updcmeps

Conversation

@DeniseWorthen
Copy link
Copy Markdown
Collaborator

@DeniseWorthen DeniseWorthen commented Oct 3, 2022

PR Checklist

  • This 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.

  • Results for one or more of the regression tests change and the reasons for the changes are understood and explained below.

  • New or updated input data is required by this PR. If checked, please work with the code managers to update input data sets on all platforms.

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 responsibility to keep the PR up-to-date with the develop branch of ufs-weather-model.

Description

Updates CMEPS to current ESCOMP/CMEPS master

Issue(s) addressed

Testing

All baselines on hera.intel and hera.gnu reproduced at commit c3c25a7

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
  • wcoss2.intel
  • acorn.intel
  • opnReqTest for newly added/changed feature
  • CI

Dependencies

@DeniseWorthen DeniseWorthen marked this pull request as ready for review October 3, 2022 12:47
@DeniseWorthen DeniseWorthen added the No Baseline Change No Baseline Change label Oct 3, 2022
@jkbk2004
Copy link
Copy Markdown
Collaborator

@DeniseWorthen We will merge in #1410 today. And then we can start working on either this PR or #1443. After reading conversation on #1443, my question is to commit the PRs separately (this pr first), right?

@DeniseWorthen
Copy link
Copy Markdown
Collaborator Author

This PR will be included in PR #1443. Closing.

@DeniseWorthen DeniseWorthen self-assigned this Feb 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

No Baseline Change No Baseline Change

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Update CMEPS for latest ESCOMP/master

2 participants