Repository navigation
[INSTALL]: gsi-ncdiag tag v1.1.3 #1938
Description
Activity
I'll take a look this week and see if it's viable to install as an add-on environment (incl. gsi-env and global-workflow-env, unless others are also needed).
@AlexanderRichert-NOAA Did you have a chance to look into this?
No I'll do that right now...
On Acorn:
spack-stack 2.0.0, oneAPI:module use /lfs/h1/emc/nceplibs/noscrub/spack-stack/spack-stack-2.0.0/envs/gsi-ncdiag-1.1.3-oneapi-2024.2.1/modules/Core && module load stack-intel-oneapi-compilers stack-cray-mpich gsi-ncdiag
spack-stack 2.0.0, Intel:module use /lfs/h1/emc/nceplibs/noscrub/spack-stack/spack-stack-2.0.0/envs/gsi-ncdiag-1.1.3-intel-19.1.3.304/modules/Core && module load stack-intel-oneapi-compilers-classic stack-cray-mpich gsi-ncdiag
spack-stack 2.1.0, oneAPI:module use /lfs/h1/emc/nceplibs/noscrub/spack-stack/spack-stack-2.1.0/envs/gsi-ncdiag-1.1.3-oneapi-2024.2.1/modules/Core && module load stack-intel-oneapi-compilers stack-cray-mpich gsi-ncdiag
spack-stack 2.1.0, Intel:module use /lfs/h1/emc/nceplibs/noscrub/spack-stack/spack-stack-2.1.0/envs/gsi-ncdiag-1.1.3-intel-19.1.3.304/modules/Core && module load stack-intel-oneapi-compilers-classic stack-cray-mpich gsi-ncdiag@RussTreadon-NOAA is there another platform where this would be useful to have?
Very few GSI developers use Acorn. Most use Gaea C6, Ursa, Hercules, Orion, or WCOSS2. This issue originated from attempts to build and run GSI with spack-stack/2.x GSI on Ursa. An Ursa installation would allow us to confirm that we can build and run
gsi.xon Ursa using spack-stack/2.x.Reacted by Alex RichertUrsa:
/contrib/spack-stack/spack-stack-2.0.0/envs/gsi-ncdiag-1.1.3-oneapi-2025.2.1
/contrib/spack-stack/spack-stack-2.0.0/envs/gsi-ncdiag-1.1.3-oneapi-2025.2.1-hpcxAlso for your awareness, for future package update needs, I would suggest trying emcenvchainer (https://github.com/AlexanderRichert-NOAA/EMCEnvChainer). It's an interactive utility for installing your own updates, so in many cases it will be faster than me/us doing the installations (though in this case it would have taken a bit of extra effort since there's not a GH release for v1.1.3). It doesn't always work just because of the complexities of Spack, but in some cases it works well and will be faster. I'm happy to assist if that's ever of interest.
Thank you @AlexanderRichert-NOAA . Let me test the Usra gsi-ncdiag-1.1.3.
Ursa test
Clone GSI
developat005343a. Buildgsi.xwithgsi-ncdiag/1.1.3. The global_4denvar regression test case successfully ran to completion usinggsi-ncdiag-1.1.3.I added the
gsi-ncdiag/1.1.3PATH,LD_LIBRARY_PATH,DYLD_LIBRARY_PATH,CPATH,CMAKE_PREFIX_PATH, andgsi_ncdiag_ROOTtogsi_ursa.intel.luabecause I could not getgsi-ncdiag/1.1.3to load withgsi_ursa.intel.lua.gsi-ncdiag/1.1.3requiresstack-intel-oneapi-compilers/2025.2.1andstack-intel-oneapi-mpi/2021.13However,
gsi_ursa.intel.luahasprepend_path("MODULEPATH", "/contrib/spack-stack/spack-stack-2.1.0/envs/ue-oneapi-2025.3.1/modules/Core") local stack_oneapi_ver=os.getenv("stack_oneapi_ver") or "2025.3.1" local stack_impi_ver=os.getenv("stack_impi_ver") or "2021.17" local oneapi_mkl_ver=os.getenv("oneapi_mkl_ver") or "2025.3"@RussTreadon-NOAA do you plan to tag a release for v1.1.3? We can use the Git repo/commit directly for Spack, but please let me know and we'll get this added to the Spack recipe.
@AlexanderRichert-NOAA : I thought creating https://github.com/NOAA-EMC/GSI-ncdiag/releases/tag/v1.1.3 was sufficient. I am not the code manager for GSI-ncdiag. Who decides when to create GSI-ncdiag releases and who creates the release?
Oh okay, I missed or forgot that- I think that should be sufficient. Thanks!
- moved this from In Progress to Done in spack-stack-2.1.x (2026 Q1)
on May 27, 2026
Package name
gsi-ncdiag
Package version/tag
1.1.3
Build options
current
Installation timeframe
As soon as possible. spack-stack/2.0.0 and spack-stack/2.1 need gsi-ncdiag v1.1.3 in order for
gsi.xto successfully run to completion. The spack-stack/2.xgsi.xseg faults when built with gsi-ncdiag v1.1.2.Other information
For additional information see