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

Intel module generation via env2 #1022

Open
shahzebsiddiqui opened this issue Oct 27, 2016 · 4 comments
Open

Intel module generation via env2 #1022

shahzebsiddiqui opened this issue Oct 27, 2016 · 4 comments

Comments

@shahzebsiddiqui
Copy link

Intel claims to use their shell scripts when loading the environment. Most HPC sites write their own intel modulefile which work for most cases however, it is not configured properly according to what Intel claims.

Please review this link and reconfigure the module file to source the script.
https://software.intel.com/en-us/articles/using-environment-modules-with-the-intel-development-tools

@ocaisa
Copy link
Member

ocaisa commented Oct 27, 2016

Are you saying the intel compiler installations from EasyBuild are not working for you? I noticed the other day that the output from the shell scripts includes MKL, IntelMPI and friends, exactly what source file are you using to build your intel installations (the EB one in the repos don't include these RPMs)?

@shahzebsiddiqui
Copy link
Author

No EasyBuild is working for Intel, the issue is the way module files are generated from EasyBuild is the not the optimal method as Intel claims. Please see link. One would need to modify the IntelBase easyblock in order to make this work. Right now I am using EasyBuild to install the software and overwriting the modulefile by doing a source on the intel script.

@ocaisa
Copy link
Member

ocaisa commented Oct 28, 2016

The script you seem to be using (psxevars.sh) is for entire Parallel Studio package (since you have things like daal, tbb and intel python inside), if you just load the intel compiler and use the scripts for the compilers (ifortvars.sh and iccvars.sh) I think you'll find that the actual differences are far less. In fact the intel scripts explicitly include mpi in their output, which we explicitly do not want in EasyBuild. Other intel packages like IntelMPI, IntelMKL, tbb, daal, etc. that come with Parallel Studio are all packaged separately in EasyBuild (on purpose).

I'm pretty certain that @boegel, @wpoely86 and the other contributors have been very careful on this front, but if you see a specific discrepancy with the software the modules are meant to be installing then definitely this can be fixed.

@boegel boegel added this to the v3.1 milestone Nov 10, 2016
@ocaisa
Copy link
Member

ocaisa commented Nov 14, 2016

And the intel installation scripts are not without flaws...take a look at #1032

@boegel boegel modified the milestones: 3.1.0, 3.2.0 Jan 30, 2017
@boegel boegel modified the milestones: 3.2.0, 3.3.0 May 2, 2017
@boegel boegel modified the milestones: 3.3.0, 3.x Jun 22, 2017
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

No branches or pull requests

3 participants