Add configuration for Intel oneAPI 2025.0.0 on Nautilus - #1382
Merged
climbfuji merged 5 commits intoNov 20, 2024
Conversation
…ites/tier1/nautilus/compilers.yaml
6 tasks
…eature/oneapi2025_nautilus_comments
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add configuration for Intel oneAPI 2025.0.0 on Nautilus. This is with
ifx, since there is no moreifortinoneapi@2025.0.0. This configuration is currently commented out, since the default is and should be 2024.2.1 withifortfor now.Testing
Built NEPTUNE standalone environment on Nautilus with
oneapi@2025.0.0and ... compiled/ran neptune with it.This requires a bug fix in
py-scipyin JCSDA/spack#483 (see there for more information and the upstream spack develop PR).Applications affected
None
Systems affected
Nautilus
Dependencies
Issue(s) addressed
Resolves #1148
Checklist