-
Notifications
You must be signed in to change notification settings - Fork 151
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 hpc stack from hpc-stack to hpc-stack-gfsv16 #560
Comments
Two sets of hpc-stacks in EPIC-maintained space were built on
(see notes for modulefile updates in There is an issue open #447 about issues with higher intel versions. Building of the GSI develop branch is successful for both intel-2018, and intel-2022. Running intel-2018 regression tests still fails for 7/9 tests. Are there any updates to be done to the regression files data or location?..
|
PR #562 merged into |
Description of the Issue
The HPC stack used in release/gfsv16 is not up-to-date for CRTM on HERA.
The updated HPC stack for gfsv16 is the hpc-stack-gfsv16 CRTM on HERA
See issues documented in global-workflow 1453
Further investigation of the HPC stacks on ORION also found that CRTM version 2.4.0 in the HPC stack is also outdated.
Issue #519 has been opened in hpc-stack repo to request updating the CRTM version 2.4.0 on all machines.
A related issue #517 was opened to update CRTM version 2.4.0 coefficients on all machines.
Based on the discussion in the GW issue #1453,
we need to do the following:
develop
uses EPIC-maintain hpc-stacks and, later, spack-stackrelease/gfsda.v16
uses hpc-stack-gfsv16On HERA, updating the hpc stack to hpc-stack-gfsv16 is ready. So, I will open a PR to update the HERA modulefiles for gfsda.v16. The updated changes can be found in gfsda.v16_crtm under emilyhcliu fork.
Here are the changes
@KateFriedman-NOAA wrote a good summary about the EIB's hpc stacks maintence. It is added here for reference:
The text was updated successfully, but these errors were encountered: