[INSTALL]: new release wgrib2/3.8.0

[Hang-Lei-NOAA]

Package name

wgrib2

Package version/tag

3.8.0

Build options

need g2c/2.3.0, libaec, netcdf

Installation timeframe

upgrade in spack-stack release and Install on all RDHPCS platforms

Other information

No response

[XiaqiongZhou-NOAA]

@Hang-Lei-NOAA : I would like to confirm that if wgrib2/3.8.0 is included in spack-stack 2.x that you mentioned.
When will the new spack-stack be available based on the schedule? is it possible to have wgrib2/3.8.0 available on GAEA/URSA before the release of new spack-stack.

[climbfuji]

This is not in spack-stack-2.0.0 (release is today). We can do this update in spack-stack-2.1.0, which is scheduled for February 2026.

[XiaqiongZhou-NOAA]

Dom: Thank for your information. Is it possible to be earlier as SFS planned to start real-time runs on Jan. We need this library as soon as possible.

[climbfuji]

Dom: Thank for your information. Is it possible to be earlier as SFS planned to start real-time runs on Jan. We need this library as soon as possible.

If someone from EPIC or EMC can create a pull request to update wgrib2 in spack-stack develop (after we merged the release branches back today/tomorrow), followed by a chained environment on a selected platform (where you want to do your real-time runs), then yes.

@rickgrubin-noaa @AlexanderRichert-NOAA FYI

[XiaqiongZhou-NOAA]

We would like to run on URSA. Thank you very much for your help!

[rickgrubin-noaa]

@XiaqiongZhou-NOAA and @AlexanderRichert-NOAA a few questions with respect to the wgrib2 spack package:

• is v3.7.0 to be accounted for, or skipped?
  • Prerequisites
    • what variants are to be turned on for this chained env build?
• this will require an update to g2c as well
  • g2c is currently built without any variant changes from defaults; is this acceptable?

[XiaqiongZhou-NOAA]

Rick: Sorry, I don’t have answers to your questions. We don’t have any specific requirements. It’s fine for us if wgrib2/3.8.0 works well with GRIB2 files using gmerge and the new version can be made available quickly.

[KarinaAsmar-NOAA]

Dom: Thank for your information. Is it possible to be earlier as SFS planned to start real-time runs on Jan. We need this library as soon as possible.

If someone from EPIC or EMC can create a pull request to update wgrib2 in spack-stack develop (after we merged the release branches back today/tomorrow), followed by a chained environment on a selected platform (where you want to do your real-time runs), then yes.

@rickgrubin-noaa @AlexanderRichert-NOAA FYI

@Hang-Lei-NOAA Is this PR something that can be done by the wgrib2 team? We are looking to use the new wgrib2 on Ursa for SFS real-time runs on Jan.

[climbfuji]

I think the easiest is if EPIC builds a chained environment on Ursa with wgrib@3.8.0 and an updated g2c with the same build options as for the earlier versions. The wgrib2 team can also do this following the instructions in the spack-stack wiki, but if the new versions are not yet known to spack then this process is a little more involved. What we definitely not want is manual installations of these spack-stack packages outside the spack-stack environments that then end up in more than just one-off testing.

[Hang-Lei-NOAA]

I agree with Dom. Actually many spack-stack installations on ursa have been difficult for many users to find which ones they need to use. Let’s wait for Epic installation through addon.

…

On Wed, Jan 7, 2026 at 1:37 PM Dom Heinzeller ***@***.***> wrote: *climbfuji* left a comment (JCSDA/spack-stack#1832) <#1832 (comment)> I think the easiest is if EPIC builds a chained environment on Ursa with ***@***.*** and an updated g2c with the same build options as for the earlier versions. The wgrib2 team can also do this following the instructions in the spack-stack wiki, but if the new versions are not yet known to spack then this process is a little more involved. What we definitely not want is manual installations of these spack-stack packages outside the spack-stack environments that then end up in more than just one-off testing. — Reply to this email directly, view it on GitHub <#1832 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKWSMFHE7RG5FUZYARZFHX34FVG6DAVCNFSM6AAAAACOB6KLK6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTOMRQGIYTOMZXHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[KarinaAsmar-NOAA]

I think the easiest is if EPIC builds a chained environment on Ursa with wgrib@3.8.0 and an updated g2c with the same build options as for the earlier versions. The wgrib2 team can also do this following the instructions in the spack-stack wiki, but if the new versions are not yet known to spack then this process is a little more involved. What we definitely not want is manual installations of these spack-stack packages outside the spack-stack environments that then end up in more than just one-off testing.

Thanks @climbfuji @Hang-Lei-NOAA ! Does anybody on EPIC need to be notified for this to be done?