User Tools

Site Tools


modules

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
modules [2016/09/22 20:30]
root
modules [2017/09/11 23:14] (current)
wlfarris
Line 70: Line 70:
 Here are some recommended module/​.bashrc setups for different cases: Here are some recommended module/​.bashrc setups for different cases:
  
-** Your run only one program, or all the programs you run use the same modules, or each uses different modules that don't conflict **+** You run only one program, or all the programs you run use the same modules, or each uses different modules that don't conflict **
  
 Put the ''​module load ...''​ in ''​.bashrc'',​ above ''​[ -z...''​. ​ The same environment will be loaded from ''​.bashrc''​ for every interactive session, batch job, and MPI program if any.  Many modules, for instance ''​R''​ and ''​matlab''​ and ''​python'',​ can be assumed to not conflict, though most of the very many combinations have not been tested. ​ Modules that definitely do conflict are MPI modules, only one may be safely used at a time, and multiple versions of the same program, like ''​gcc/​4.7.1''​ and ''​gcc/​4.9.1''​. ​ Multiple compilers, such as ''​gcc''​ and ''​intel''​ usually don't conflict, but for MVAPICH2 and OpenMPI, the compiler module is used to load the MPI module, so multiple compiler modules should be loaded in order (1) compiler module you want to use with MPI (2) MPI module (3) additional compiler module. ​ In some cases, gnu MPI programs using MKL libraries can want a library only available from the Intel compiler, so a combination like ''​module load gcc/4.7.2 mkl/14.0.3 openmpi/​1.8.8;​module load intel/​14.0.3''​ may be necessary. ​ The last ''​intel/​14.0.3''​ may show a harmless warning message. Put the ''​module load ...''​ in ''​.bashrc'',​ above ''​[ -z...''​. ​ The same environment will be loaded from ''​.bashrc''​ for every interactive session, batch job, and MPI program if any.  Many modules, for instance ''​R''​ and ''​matlab''​ and ''​python'',​ can be assumed to not conflict, though most of the very many combinations have not been tested. ​ Modules that definitely do conflict are MPI modules, only one may be safely used at a time, and multiple versions of the same program, like ''​gcc/​4.7.1''​ and ''​gcc/​4.9.1''​. ​ Multiple compilers, such as ''​gcc''​ and ''​intel''​ usually don't conflict, but for MVAPICH2 and OpenMPI, the compiler module is used to load the MPI module, so multiple compiler modules should be loaded in order (1) compiler module you want to use with MPI (2) MPI module (3) additional compiler module. ​ In some cases, gnu MPI programs using MKL libraries can want a library only available from the Intel compiler, so a combination like ''​module load gcc/4.7.2 mkl/14.0.3 openmpi/​1.8.8;​module load intel/​14.0.3''​ may be necessary. ​ The last ''​intel/​14.0.3''​ may show a harmless warning message.
modules.txt · Last modified: 2017/09/11 23:14 by wlfarris