Intel
We are in the process of migrating all software documentation from LONI Docs. If the current page is incomplete, please visit LONI Docs. We apologize for the inconvenience.
Table of Content
About
The Intel compiler suite is the default development environment on the HPC@LSU clusters.
Version and Availability
Softenv Keys for Intel on louie
| Machine | Version | Softenv Key |
|---|---|---|
| louie | 11.1 | +intel-cc-11.1 |
| louie | 11.1 | +intel-fc-11.1 |
| louie | 10.2 | +intel-mkl-10.2 |
▶ Display Softenv Keys for Intel all clusters
| Machine | Version | Softenv Key |
|---|---|---|
| eric | 11.1 | +intel-cc-11.1 |
| eric | 11.1 | +intel-fc-11.1 |
| eric | 10.2 | +intel-mkl-10.2 |
| qb | 10.1 | +intel-cc-10.1 |
| qb | 11.1 | +intel-cc-11.1 |
| qb | 10.1 | +intel-fc-10.1 |
| qb | 11.1 | +intel-fc-11.1 |
| qb | 10.2 | +intel-mkl-10.2 |
| oliver | 11.1 | +intel-cc-11.1 |
| oliver | 11.1 | +intel-fc-11.1 |
| oliver | 10.2 | +intel-mkl-10.2 |
| louie | 11.1 | +intel-cc-11.1 |
| louie | 11.1 | +intel-fc-11.1 |
| louie | 10.2 | +intel-mkl-10.2 |
| poseidon | 11.1 | +intel-cc-11.1 |
| poseidon | 11.1 | +intel-fc-11.1 |
| poseidon | 10.2 | +intel-mkl-10.2 |
| painter | 11.1 | +intel-cc-11.1 |
| painter | 11.1 | +intel-fc-11.1 |
| painter | 10.2 | +intel-mkl-10.2 |
| tezpur | 10.2 | +intel-mkl-10.2 |
| tezpur | 11.1 | +intel-cc-11.1 |
| tezpur | 11.1 | +intel-fc-11.1 |
| philip | 10.1 | +intel-cc-10.1 |
| philip | 10.1 | +intel-fc-10.1 |
| philip | 10.1 | +intel-mkl-10.1 |
| philip | 10.2 | +intel-mkl-10.2 |
| philip | 11.1 | +intel-cc-11.1 |
| philip | 11.1 | +intel-fc-11.1 |
| philip | 12.1 | +intel-12.1 |
| philip | 13.1.0 | +intel-13.1.0 |
| supermike2 | 12.1.4 | +Intel-12.1.4 |
| supermike2 | 13.0.0 | +Intel-13.0.0 |
▶ Softenv FAQ?
The information here is applicable to LSU HPC and LONI systems.
Softenv
SoftEnv is a utility that is supposed to help users manage complex user environments with potentially conflicting application versions and libraries.
System Default Path
When a user logs in, the system /etc/profile or /etc/csh.cshrc (depending on login shell, and mirrored from csm:/cfmroot/etc/profile) calls /usr/local/packages/softenv-1.6.2/bin/use.softenv.sh to set up the default path via the SoftEnv database.
SoftEnv looks for a user's ~/.soft file and updates the variables and paths accordingly.
Viewing Available Packages
Using the softenv command, a user may view the list of available packages. Currently, it can not be ensured that the packages shown are actually available or working on the particular machine. Every attempt is made to present an identical environment on all of the LONI clusters, but sometimes this is not the case.
Example,
$ softenv These are the macros available: * @default These are the keywords explicitly available: +amber-8 Applications: 'Amber', version: 8 Amber is a +apache-ant-1.6.5 Ant, Java based XML make system version: 1.6. +charm-5.9 Applications: 'Charm++', version: 5.9 Charm++ +default this is the default environment...nukes /etc/ +essl-4.2 Libraries: 'ESSL', version: 4.2 ESSL is a sta +gaussian-03 Applications: 'Gaussian', version: 03 Gaussia ....
Listing of Available Packages
See Packages Available via SoftEnv on LSU HPC and LONI.
For a more accurate, up to date list, use the softenv command.
Caveats
Currently there are some caveats to using this tool.
- packages might be out of sync between what is listed and what is actually available
- resoft and soft utilities are not; to update the environment for now, log out and login after modifying the ~/.soft file.
Availability
softenv is available on all LSU HPC and LONI clusters to all users in both interactive login sessions (i.e., just logging into the machine) and the batch environment created by the PBS job scheduler on Linux clusters and by loadleveler on AIX clusters..
Packages Availability
This information can be viewed using the softenv command:
% softenv
Managing Environment with SoftEnv
The file ~/.soft in the user's home directory is where the different packages are managed. Add the +keyword into your .soft file. For instance, ff one wants to add the Amber Molecular Dynamics package into their environment, the end of the .soft file should look like this:
+amber-8
@default
To update the environment after modifying this file, one simply uses the resoft command:
% resoft
Usage
Select the desired compiler name (possibly including an option) from the following table under the type of code being developed:
| Language | Serial Codes | MPI Codes | OpenMP Codes | Hybrid Codes |
|---|---|---|---|---|
| Fortran | ifort | mpif90 | ifort -openmp | mpif90 -openmp |
| C | icc | mpicc | icc -openmp | mpicc -openmp |
| C++ | icpc | mpiCC | icpc -openmp | mpiCC -openmp |
If you are compiling an MPI program, make sure you use an MPI library that was built with the version of compiler you choose. The softenv key names provide that information. For example, using the MVAPICH2 version 1.9a2 library with the 13.0.0 version of the Intel compiler would be specified with keys that look something like:
+Intel-13.0.0 +mvapich2-1.9a2-Intel-13.0.0
Of course, always verify what is available on the machine you choose to use. Checking what command would be selected is as simple as:
[user@mach1 ~]$ which mpif90 /usr/local/packages/openmpi/1.6.2/Intel-13.0.0/bin/mpif90 [user@mach1 ~]$
This shows that the OpenMPI is set as the MPI library of choice, along with the 13.0.0 release of the Intel compiler.
▶ Softenv FAQ?
The information here is applicable to LSU HPC and LONI systems.
Softenv
SoftEnv is a utility that is supposed to help users manage complex user environments with potentially conflicting application versions and libraries.
System Default Path
When a user logs in, the system /etc/profile or /etc/csh.cshrc (depending on login shell, and mirrored from csm:/cfmroot/etc/profile) calls /usr/local/packages/softenv-1.6.2/bin/use.softenv.sh to set up the default path via the SoftEnv database.
SoftEnv looks for a user's ~/.soft file and updates the variables and paths accordingly.
Viewing Available Packages
Using the softenv command, a user may view the list of available packages. Currently, it can not be ensured that the packages shown are actually available or working on the particular machine. Every attempt is made to present an identical environment on all of the LONI clusters, but sometimes this is not the case.
Example,
$ softenv These are the macros available: * @default These are the keywords explicitly available: +amber-8 Applications: 'Amber', version: 8 Amber is a +apache-ant-1.6.5 Ant, Java based XML make system version: 1.6. +charm-5.9 Applications: 'Charm++', version: 5.9 Charm++ +default this is the default environment...nukes /etc/ +essl-4.2 Libraries: 'ESSL', version: 4.2 ESSL is a sta +gaussian-03 Applications: 'Gaussian', version: 03 Gaussia ....
Listing of Available Packages
See Packages Available via SoftEnv on LSU HPC and LONI.
For a more accurate, up to date list, use the softenv command.
Caveats
Currently there are some caveats to using this tool.
- packages might be out of sync between what is listed and what is actually available
- resoft and soft utilities are not; to update the environment for now, log out and login after modifying the ~/.soft file.
Availability
softenv is available on all LSU HPC and LONI clusters to all users in both interactive login sessions (i.e., just logging into the machine) and the batch environment created by the PBS job scheduler on Linux clusters and by loadleveler on AIX clusters..
Packages Availability
This information can be viewed using the softenv command:
% softenv
Managing Environment with SoftEnv
The file ~/.soft in the user's home directory is where the different packages are managed. Add the +keyword into your .soft file. For instance, ff one wants to add the Amber Molecular Dynamics package into their environment, the end of the .soft file should look like this:
+amber-8
@default
To update the environment after modifying this file, one simply uses the resoft command:
% resoft
Compiler Options
The behavior of the compiler can be controlled with command line options. There are way to many to list, but a few of the more commonly used ones include:
| -g | Enable debugging |
| -O0 | Inhibit optimization |
| -O2 | Default optimization - loop unrolling, loop-invariant code movement, constant and copy propagation, dead code elimination, etc. |
| -O3 | Aggressive optimization - -O2 plus prefetching, scalar replacement, loop transformation, etc. |
| -FR | Fortran 90 free format input files. |
| -ip/ipo | Enable inline function expansion within the current source file or multiple files. |
| -axT | Automatic processor-specific optimization for Intel Core 2 Duo processor family |
Resources
- See the manpages (i.e.
man ifort) for usage details.
Last modified: March 07 2013 12:30:04.