Difference: PALMA3 (17 vs. 18)

Revision 182017-03-01 - HolgerAngenent

Line: 1 to 1
 
META TOPICPARENT name="HPC"

PALMA-NG

Line: 27 to 27
  The most important difference between Palma I and palma-ng is the new introduced hierarchical module naming scheme (2)
Added:
>
>
(1) https://www.tacc.utexas.edu/research-development/tacc-projects/lmod

(2) https://hpcugent.github.io/easybuild/files/hust14_paper.pdf

 
Command (Short- and Long-form) Meaning
module av[ailable] Lists all currently available modules
module spider List all available modules with their description
Line: 37 to 41
 
module rm modul1 modul2 ... Deletes module from the current environment
module purge Deletes all modules from current environment
Changed:
<
<
(1) https://www.tacc.utexas.edu/research-development/tacc-projects/lmod
>
>
Hierarchical module naming scheme means that you do not see all modules at the same time. You will have to load a toolchain or compiler first to see the software that has been compiled with those. At the moment there are the following toolchains:
 
Changed:
<
<
(2) https://hpcugent.github.io/easybuild/files/hust14_paper.pdf
>
>
  • foss/2016b and foss/2017a GCC with OpenMPI
  • intel/2016b and intel/2017a Intel Compiler with Intel MPI
  • goolfc/2016.10 Only on the k20gpu nodes for CUDA

If you want to use the Intel compiler, you can type for example the following:

module add intel/2016b
module av

and you will see the software that has been compiled with this version. Alternatively you can use the "module spider" command.

 

Using the module command in submit scripts

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2022 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding ZIVwiki? Send feedback
Datenschutzerklärung Impressum