Open DavidHuber-NOAA opened 1 month ago
It looks like things are moving along in the UFS, so I am un-blocking this.
The spack-stack developers expect version 1.9.0 to be more stable and robust than 1.8.0. I have renamed this issue to reflect that we should move to 1.9.0 instead of 1.8.0 and will reapply the blocked label until the weather model upgrades to 1.9.0.
What new functionality do you need?
The global-workflow and subcomponents should all be upgraded to spack-stack 1.8.0. Among other things, this upgrade will allow the workflow to use the same Python and BUFR libraries across all subcomponents. There will still be a need for a "
gsi-addon
" environment (a misnomer as of 1.8.0) to enable the use of MET/METplus 9.1.3/3.1.1 in EMC_verif-global, but this environment will include all of the same modules as theunified-dev
environment. Also, an upstream requirement not yet in spack-stack 1.8.0 environments is CRTM v3.1.1, which will need to be incorporated into (at least) the GSI, UPP, UFS, and GDASApp.Upstream Issues/PRs
What are the requirements for the new functionality?
Acceptance Criteria
All builds and CI tests are successful on all tier-1 platforms:
Ideally all builds and tests are successful on tier-2 platforms as well:
Suggest a solution (optional)
No response