release/1.9.0: Update s4 to use intel oneapi 2024#1475
release/1.9.0: Update s4 to use intel oneapi 2024#1475climbfuji merged 3 commits intoJCSDA:release/1.9.0from
Conversation
climbfuji
left a comment
climbfuji
left a comment
There was a problem hiding this comment.
Took a sneak peek. If you want to be able to use both, the current Intel Classic and the new oneAPI, split packages.yaml into three files (see, for example, the Nautilus site config): packages.yaml (common stuff), packages_intel.yaml, packages_oneapi.yaml.
Thank you, I will look into Nautilus config and follow it. |
|
What tests should I run to check if the modifications don't break anything? I installed the unified environment with the change and everything went smoothly. |
JCSDA and EMC are using S4, they should be able to help |
climbfuji
changed the title
|
@InnocentSouopgui-NOAA Since you are only updating the S4 site config, please make sure to run this before pushing branch updates to github.com: Thanks! |
I will make sure of that the next time. |
InnocentSouopgui-NOAA
requested review from
AlexanderRichert-NOAA,
climbfuji and
eap
InnocentSouopgui-NOAA
force-pushed
the
feature/s4-oneapi2024
branch
from
2cbd763 to
6fe530b
Compare
2 participants
Summary
Update S4 configs to use Intel OneApi 2024
Testing
Describe the testing done for this PR.
Applications affected
List all known applications (UFS WM, JEDI, SRW, etc.) intentionally or unintentionally affected by this PR.
Systems affected
S4
Dependencies
If there are PRs that need to be merged before or along with this one, please add "- [ ] waiting on LINK_TO_PR" for each of them
Issue(s) addressed
Link the issues addressed or resolved by this PR (use
Fixes #???for fully resolved issues)Checklist