- Infos im HLRS Wiki sind nicht rechtsverbindlich und ohne Gewähr -

Module environment(Hawk)

From HLRS Platforms
Revision as of 12:39, 14 January 2020 by Hpcbjdic (talk | contribs)
Jump to navigationJump to search

Hints for users

A module environment is used on Hawk in order to allow for flexibly choosing software to be used out of a large set. In order to use a particular software, you first have to load the respective module. A set of default modules is already loaded after login.

A new implementation of the module command is used on Hawk in order to allow for improved user experience. However, the same sub-commands are available as known from former systems. The layout of outputs yet slightly differs. Furthermore, not all available modules might be shown right after login (cf. below).

Basic commands:

  • show available modules: module avail or module avail <substring to be searched for>
  • show brief description for a given module: module whatis <modulename>
  • (un)load a module: module (un)load <modulename>
  • swap modules: module swap <old module> <new module>
  • show loaded modules: module list
  • show help for a specific module: module help <modulename>
  • search for keywords (e.g. “compiler”, “debugger”, etc.) in module descriptions: module keyword <keyword>

Please have a look on here w.r.t. further functionality.

In order to work properly, applications built with a given compiler and MPI need to be linked with libraries built with the very same compiler and MPI. The module mechanism deployed on Hawk supports you in doing so by providing only those modules built with the currently loaded compiler and MPI. In case of swapping the compiler and/or MPI, available and loaded modules are also swapped in order to match with the new compiler/MPI.