Changes between Initial Version and Version 1 of Public/User_Guide/Information_on_software


Ignore:
Timestamp:
Jul 7, 2016, 9:02:41 AM (8 years ago)
Author:
Anke Kreuzer
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Public/User_Guide/Information_on_software

    v1 v1  
     1= General information =
     2
     3== Modules ==
     4
     5Based on the requirements by the DEEP applications several software tools have already been installed on the DEEP system. To see which modules are available use
     6
     7''module avail''
     8
     9For most tools and compilers there are several versions available, you can list the different versions of a specific tool with module avail “tool name”, for example
     10
     11{{{
     12-bash-4.1$ module avail intel
     13
     14------------------------------------------------------------------------------ /usr/local/modulefiles/COMPILER --------------------------------
     15intel/13.0.4        intel/14.0.3        intel/15.0          intel/15.2.164      intel/16.0          intel/16.2(default) intel/16.3
     16}}}
     17
     18You can load a specific version or just use the default with for example
     19
     20''module load intel''
     21
     22The modules which are currently loaded can be listed with the command “module list”. To unload a module just type “module unload” followed by the name of the module.
     23
     24
     25== Compiler ==
     26
     27There are several compilers available, but as it is highly recommended to use the Intel compiler on the KNC system it might be best to also use it on the DEEP system.\\
     28Installed compilers:\\
     29* Intel compiler: module load intel
     30* GNU compiler:  module load gcc
     31* PGI Compiler: module load pgi
     32
     33
     34== Profiling and analysis tools ==
     35
     36VTune:    module load VTune\\
     37Extrae:   module load UNITE extrae\\
     38Scalasca: module load UNITE scalasca
     39
     40== MPI programs ==
     41It is recommended to start parallel MPI Jobs on the DEEP Cluster using the mpiexec from the ParaStation MPI installation. Generally all MPI implementations using PMI are supposed to work with the ParaStation mpiexec. For instance you can compile your application using Intel MPI and launch your job with mpiexec from Parastation. The Intel mpirun will not work.