-
Notifications
You must be signed in to change notification settings - Fork 4
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
Software request: Intel compiler and MKL libraries #1
Comments
@thomsonk it would be good to get an update on the plan for this. |
Short-term work-around: while the full Intel compiler is not yet on hand: in the CC stack there is an imkl version available to the public for run-time usage when programs are already compiled for MKL.
|
Further work is in progress regarding Intel compiler licensing and this ticket will be update when details are known. |
Just thought I'd mention the tracking issue on the CC side that would allow building software with a local Intel compiler on top of the Intel based modules of the CC software stack. |
It was recently discovered that since this ticket was open Intel oneAPI compiler (base toolkit + HPC toolkit) is now available for unrestricted commercial use, with an update to Intel's license terms effective Dec. 2020.
NRC plan for implementation:Provided the above now meets license requirements with-out special approval necessary, the Intel compiler and toolchain can be installed on trixie cluster for general use by all researchers. Integration with Compute Canada stack will be targeted and final terms & conditions of use reviewed by NRC. This ticket is to be discussed for approval internal to IT operations meeting, in order to proceed with the install. |
Intel OneAPI Base Toolkit 2022.1.2.146 install in progress. In preparation:
|
Move installed directory into shared path, update unix ownership & permissions. |
Generate modulefiles/ using Intel-provided modulefiles-setup.sh and add to MODULEPATH across nodes. |
Install Intel OneAPI HPC Toolkit 2022.1.2.117. Regenerate modulefiles and checked that mpiifort and ifort, icc appear in PATH after module load mpi mkl icc. |
Ran samples from https://github.com/oneapi-src/oneAPI-samaples.git
|
Intel compiler is installed, two options for site-local evaluation CC CVMFS integration - as per CC CVMS pull#6:
Then the config can be checked to see if it enables the local restricted path to support icc,, ifort, mpiic, etc. binaries from |
@itamblyn : Can this issue be resolved now? |
👍 Thanks! |
No description provided.
The text was updated successfully, but these errors were encountered: