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

Release/public v2 - ufs-WM #304

Conversation

natalie-perlin
Copy link
Collaborator

@natalie-perlin natalie-perlin commented Jun 11, 2022

(may not need merging in its present form, uses local builds of the hpc-stack on cheyenne)

DESCRIPTION OF CHANGES:

  1. Use repositories branch/hash :
  • ufs-community/ufs-weather-model branch=release-public-v3-SRW
  • NOAA-EPIC/regional_workflow branch=feature/hera-fix
  • ufs-community/UFS_UTILS hash = 31271f7
  • NOAA-EMC/UPP hash = 1dbcb0c4
  1. Fixes for Cheyenne compilers and SRW builds

  2. Temporary directory for the HPC-stack built to match the package versions required for the ufs-weather-model, as well as sync with other platforms

TESTS CONDUCTED:

HPC-stack built on Cheyenne for intel/2022:

/glade/scratch/nperlin/HPC-stack/intel2022.1/install-1.2.0/

HPC-stack on Cheyenne- GNU11.2 build:
/glade/scratch/nperlin/HPC-stack/gnu11.2/install-1.2.0/

SRW app built successfully with both Intel/2022.1 and GNU11.2.

ISSUE (optional):

  • This PR is resolving module dependence issues for cheyenne for intel/2022 and packages needed for SRW release/public-v2;
    Updates with the compilers and modules on Cheyenne are related to the PR#250

  • ufs-weather-model branch release-public-v2-SRW is checked out during the SRW build

CONTRIBUTORS (optional):

@mark-a-potts

@jkbk2004
Copy link
Collaborator

@natalie-perlin I have to point out that this PR should be combined with #250. Either close #250 or combine together. Furthermore, scratch on Cheyenne is not persistent. Single hpc-stack location is always preferable across UFS applications. If the change is not ready to merge in, I recommend to put on issue or draft PR first. Once its on PR list, we will start use to use resources,

@jkbk2004
Copy link
Collaborator

@EdwardSnyder-NOAA can we combine two PRs together (#250 and this PR) ?

@natalie-perlin
Copy link
Collaborator Author

Closing the PR that was successfully used for testing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants