Skip to content

Update gsibec 1.4.2 -> 1.4.4 - #2137

Merged
climbfuji merged 3 commits into
JCSDA:developfrom
eap:feature/gsibec-update
Sep 30, 2026
Merged

climbfuji merged 3 commits into
JCSDA:developfrom
eap:feature/gsibec-update

Conversation

@eap

@eap eap commented Sep 29, 2026

Copy link
Copy Markdown
Collaborator

No description provided.

@climbfuji

Copy link
Copy Markdown
Collaborator

More than a year ago, it was discussed that NOAA was going to test with MKL when using Intel/IntelLLVM instead of openblas, and then switch over to match the other partners (all others: Intel/IntelLLVM use MKL, GNU/LLVM native use OpenBLAS).

This still hasn't happened, hence the need to touch 14 files here.

The irony is that before we introduced spack-stack, NOAA was using hpc-stack and JCSDA was using jedi-stack, and both of them had Intel with MKL :-)

@rickgrubin-noaa

Copy link
Copy Markdown
Contributor

More than a year ago, it was discussed that NOAA was going to test with MKL when using Intel/IntelLLVM instead of openblas, and then switch over to match the other partners (all others: Intel/IntelLLVM use MKL, GNU/LLVM native use OpenBLAS).

This still hasn't happened, hence the need to touch 14 files here.

The irony is that before we introduced spack-stack, NOAA was using hpc-stack and JCSDA was using jedi-stack, and both of them had Intel with MKL :-)

mkl isn't a variant in repos/spack_repo/builtin/packages/gsibec/package.py -- there is this check instead:

def cmake_args(self):
        return [
            self.define("ENABLE_MKL", self.spec.satisfies("^[virtuals=lapack] intel-oneapi-mkl"))
        ]

so it would be OK to remove +mkl and ~mkl from the config yamls and achieve the desired result, yes?

@climbfuji

Copy link
Copy Markdown
Collaborator

More than a year ago, it was discussed that NOAA was going to test with MKL when using Intel/IntelLLVM instead of openblas, and then switch over to match the other partners (all others: Intel/IntelLLVM use MKL, GNU/LLVM native use OpenBLAS).
This still hasn't happened, hence the need to touch 14 files here.
The irony is that before we introduced spack-stack, NOAA was using hpc-stack and JCSDA was using jedi-stack, and both of them had Intel with MKL :-)

mkl isn't a variant in repos/spack_repo/builtin/packages/gsibec/package.py -- there is this check instead:

def cmake_args(self):
        return [
            self.define("ENABLE_MKL", self.spec.satisfies("^[virtuals=lapack] intel-oneapi-mkl"))
        ]

so it would be OK to remove +mkl and ~mkl from the config yamls and achieve the desired result, yes?

Even better ;-) but what I said above is still valid in general for the environment and should probably be resolved.

@climbfuji

Copy link
Copy Markdown
Collaborator

I'll approve and merge after #2136 went in. Then I'll issue a follow-up PR to clean up the unnecessary ~mkl variants for gsibec, since the package doesn't have the variant.

@mathomp4

Copy link
Copy Markdown
Collaborator

Once all is happy, I can make a gsibec 1.5.0 pair-of-PRs

@climbfuji
climbfuji merged commit 4cad34d into JCSDA:develop Sep 30, 2026
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants