-
Notifications
You must be signed in to change notification settings - Fork 47
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
release/1.9.0: Update s4 to use intel oneapi 2024 #1475
base: release/1.9.0
Are you sure you want to change the base?
release/1.9.0: Update s4 to use intel oneapi 2024 #1475
Conversation
…trap mirrors (JCSDA#1473) Update util/nrl/batch_install.sh: a. Add capability to create and use bootstrap mirrors b. Define function fix_permissions and use it to set the correct permissions for caches (mirrors) in developer mode, and for environments in installer mode
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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 |
@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. |
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