| Next revision | Previous revisionLast revisionBoth sides next revision |
| doku:modules [2015/05/27 13:35] – created jz | doku:modules [2023/02/17 16:33] – msiegel |
|---|
| ===== 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: | 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: |
| <code> | <code> |
| /opt/sw/x86_64/glibc-2.12/ivybridge-ep/modules/3.2.6/gnu-4.4.7/Modules/3.2.6/init/.modulespath</code> | /opt/sw/x86_64/glibc-2.12/ivybridge-ep/modules/3.2.6/gnu-4.4.7/Modules/3.2.6/init/.modulespath</code> |
| | |
| | The current contents (2015-05-27) are: |
| | |
| | <code> |
| | # |
| | # @(#)$Id: .modulespath.in,v 1.3.14.1 2007/02/22 23:13:09 rkowen Exp $ |
| | # Module version 3.2.6 |
| | # init/.modulespath. Generated from .modulespath.in by configure. |
| | # |
| | # Modulepath initial setup |
| | # ======================== |
| | # |
| | # This file defines the initial setup for the module files search path. |
| | # Comments may be added anywhere, which begin on # and continue until the |
| | # end of the line |
| | # Each line containing a single path will be added to the MODULEPATH |
| | # environment variable. You may add as many as you want - just |
| | # limited by the maximum variable size of your shell. |
| | # |
| | /opt/sw/Modules/Application-Software:/opt/sw/Modules/Debugging-and-Profiling:/opt/sw/Modules/Compiler:/opt/sw/Modules/Parallel-Environment:/opt/sw/Modules/Libraries:/opt/sw/Modules/Development:/opt/sw/Modules/V2C2:/opt/sw/Modules/TUWien:/opt/sw/Modules/BOKU:/opt/sw/Modules/ADMIN # </code> |