Differences

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

--- doku:modules [2015/05/27 13:37] – jz
+++ doku:modules [2023/02/17 16:33] – msiegel
@@ Line 1: / Line 1: @@
-===== Module environment on VSC-3 =====
+===== Modules =====
+On VSC-4 and VSC-5, spack is used to install and provide modules, see [[doku:spack|SPACK - a package manager for HPC systems]].
+==== Module environment ====
+In order to set environment variables needed for a specific application, the **module** environment may be used:
+  * ''module avail''     lists the **available** Application-Software, Compilers, Parallel-Environment, and Libraries
+  * ''module list''      shows currently loaded package of your session
+  * ''module unload <xyz>'' unload a particular package <xyz> from your session
+  * ''module load <xyz>'' load a particular package <xyz> into your session
+  * ''module display <xyz>'' OR ''module show <xyz>'' show module details such as the full  path  of  the module file and all (or most) of the environment changes the modulefile will make if loaded
+  * ''module purge'' unloads all loaded modulefiles
+== Note: ==
+  - **<xyz>** format corresponds exactly to the output of ''module avail''. Thus, in order to load or unload a selected module, copy and paste exactly the name listed by ''module avail''.\\
+  - a list of ''module load/unload'' directives may also be included in the top part of a job submission script\\
+When all required/intended modules have been loaded, user packages may be compiled as usual.
+==== Module environment on VSC-3 ====
 If a new directory in the top level of the module directory structure is created, the MODULEPATH environment variable needs to be adjusted in this file: