[INSTALL]: gsi-ncdiag/1.1.2, bufr/11.7.0, met/9.1.3, metplus/3.1.1

[DavidHuber-NOAA]

Package name

gsi-ncdiag, bufr, met, and metplus

Package version/tag

1.1.2, 11.7.0, 9.1.3, and 3.1.1, respectively

Build options

BUILD_TYPE=Release for all

Installation timeframe

I would like these to be added into the 1.5.0 installations so that the GSI, UFS_Utils, etc, can use the same spack-stack as the UFS once PR ufs-community/ufs-weather-model#1920 is merged. If we could start with Hera and Orion, that would be great, with a preference for Hera.

Other information

Work was performed to fix the interface between the GSI and bufr/12.0.0, but there are optimization (run time) issues still to be resolved, so we would like to continue using 11.7.0 for the time being until those can be resolved.

gsi-ncdiag/1.1.2 is an upgrade and fixes a memory over-allocation in the GSI.

MET and METplus are used for the global verification system (verif-global).

@AlexanderRichert-NOAA installed a test environment for the global workflow with these versions and with spack-stack-1.4.1. This was used to compile the GSI, GSI-Utils, GSI-Monitor, GFS-Utils, and UFS_Utils packages and then run the global workflow. Tests were successful at C96/C48 and C384/C192 resolutions (see NOAA-EMC/global-workflow#1868 for more details).

---

Install round 1

• Hera: /scratch1/NCEPDEV/nems/role.epic/spack-stack/spack-stack-1.5.1/envs/gsi-addon/install/modulefiles/Core
• Orion: /work/noaa/epic/role-epic/spack-stack/orion/spack-stack-1.5.1/envs/gsi-addon/install/modulefiles/Core
• Jet: /mnt/lfs4/HFIP/hfv3gfs/role.epic/spack-stack/spack-stack-1.5.1/envs/gsi-addon/install/modulefiles/Core
• Gaea C5: /lustre/f2/dev/wpo/role.epic/contrib/spack-stack/c5/spack-stack-1.5.1/envs/gsi-addon/install/modulefiles/Core
• Hercules: /work/noaa/epic/role-epic/spack-stack/hercules/spack-stack-1.5.1/envs/gsi-addon/install/modulefiles/Core
• S4: /data/prod/jedi/spack-stack/spack-stack-1.5.1/envs/gsi-addon/install/modulefiles/Core

Checked for/added gsi-ncdiag@1.1.2, added wrf-io@1.2.0 and sfcio@1.4.1
How to add wrf-io@1.2.0 / sfcio@1.4.1 ? They are already installed in the upstream environment, therefore:

spack install --add --verbose wrf-io 2>&1 | tee envs/gsi-addon/log.install.wrf-io-1.2.0
spack install --add --verbose sfcio@1.4.1 2>&1 | tee envs/gsi-addon/log.install.sfcio-1.4.1
spack module lmod refresh --upstream-modules

• Hera: /scratch1/NCEPDEV/nems/role.epic/spack-stack/spack-stack-1.5.1/envs/gsi-addon/install/modulefiles/Core
• Orion: /work/noaa/epic/role-epic/spack-stack/orion/spack-stack-1.5.1/envs/gsi-addon/install/modulefiles/Core
• Jet: /mnt/lfs4/HFIP/hfv3gfs/role.epic/spack-stack/spack-stack-1.5.1/envs/gsi-addon/install/modulefiles/Core
• Gaea C5: /lustre/f2/dev/wpo/role.epic/contrib/spack-stack/c5/spack-stack-1.5.1/envs/gsi-addon/install/modulefiles/Core
• Hercules: /work/noaa/epic/role-epic/spack-stack/hercules/spack-stack-1.5.1/envs/gsi-addon/install/modulefiles/Core
• S4: /data/prod/jedi/spack-stack/spack-stack-1.5.1/envs/gsi-addon/install/modulefiles/Core

[AlexanderRichert-NOAA]

@DavidHuber-NOAA would it be better from Global Workflow's perspective if ufs-community/ufs-weather-model#1920 used these chained environments instead? In other words, if the 1.5.0-based environment we add bufr 11.7.0 and gsi-ncdiag 1.1.2 into is called "gw-env", then would it make sense (or make any difference) for the MODULEPATH setting in UFS to point to /path/to/spack-stack-1.5.0/gw-env/install/modulefiles/Core as opposed to /path/to/spack-stack-1.5.0/unified-env/install/modulefiles/Core ?

[DavidHuber-NOAA]

Hmm, it would be nice if we could all get along and use the same environment. However, I don't think that it is necessary in this case. So I guess I would say yes, it would be better from the global workflow's perspective, but I wouldn't want to add significant work to PR1920.

On a different note, I recall now that there are two additional libraries we discussed adding: met/9.1.3 and metplus/3.1.1. Could that also be added in to this environment for the verif-global package? I believe the dependencies for these packages could remain the same as for met/10.x metplus/4.x (i.e. you could build with bufr/11.7.0 or bufr/12.0.0, either way would be fine). I will amend my title/answers above.

[AlexanderRichert-NOAA]

Yep no problem

[climbfuji]

Can we at some point in the near future try to converge to the latest versions of these packages so that we only need to install one version of each? Happy to set up a meeting to discuss this. Thanks!

[DavidHuber-NOAA]

@climbfuji There is work ongoing to fix some overly long runtimes with bufr/12 within the GSI. I suspect an upgrade to BUFR will be coming along soon that the GSI can use.

As for met and metplus, I am afraid that the system these are needed for (verif-global) will not go through the upgrade process to implement newer versions of those libraries. There is a replacement on the horizon (EVS), but there isn't a timeline for that at the moment. That said, verif-global can be run offline and stick with the current hpc-stack installs, so the installation of met/metplus isn't critical. So if it is a significant effort/difficulty, we can move forward without installing these older versions in spack-stack.

[DavidHuber-NOAA]

FYI @aerorahul