Skip to content
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

Open
wants to merge 6 commits into
base: release/1.9.0
Choose a base branch
from

Conversation

InnocentSouopgui-NOAA
Copy link
Collaborator

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

  • This PR addresses one issue/problem/enhancement, or has a very good reason for not doing so.
  • These changes have been tested on the affected systems and applications.
  • All dependency PRs/issues have been resolved and this PR can be merged.

climbfuji and others added 2 commits January 28, 2025 05:36
…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
Copy link
Collaborator

@climbfuji climbfuji left a 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.

@InnocentSouopgui-NOAA
Copy link
Collaborator Author

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.

@InnocentSouopgui-NOAA
Copy link
Collaborator Author

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.

@climbfuji
Copy link
Collaborator

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 climbfuji changed the base branch from develop to release/1.9.0 January 30, 2025 12:26
@climbfuji climbfuji changed the title Update s4 to use intel oneapi 2024 release/1.9.0: Update s4 to use intel oneapi 2024 Jan 30, 2025
@climbfuji
Copy link
Collaborator

@InnocentSouopgui-NOAA Since you are only updating the S4 site config, please make sure to run this before pushing branch updates to github.com:

git commit --allow-empty -m "[skip ci]"

Thanks!

@InnocentSouopgui-NOAA
Copy link
Collaborator Author

@InnocentSouopgui-NOAA Since you are only updating the S4 site config, please make sure to run this before pushing branch updates to github.com:

git commit --allow-empty -m "[skip ci]"

Thanks!

I will make sure of that the next time.

@InnocentSouopgui-NOAA InnocentSouopgui-NOAA marked this pull request as ready for review February 6, 2025 22:41
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.

2 participants