Software Modules #

In addition to the core software tools that are available by default, additional software is available via different Software Repositories. Note that some of these software tools are installed and maintained by other users or research groups of the cluster who have kindly agreed on sharing their efforts with other cluster users. Currently known and publicly shared repositories are:

To get access to the software available in one or more of these repositories, load the repository using module load <repos> (on command line and in script). After loading a software repository, all of its software tools are available as environment modules, that is, they can in turn be loaded using module load <software>.

Example #

The R software is available in software repository CBI. To use that R installation, first make sure to enable (“load”) the repository and then the software as in:

module load CBI   ## Enables the software repository
module load r     ## Enables R

or, shorter (order is important):

module load CBI r

After this, the R and the Rscript commands are available on the search path (PATH), e.g.

$ Rscript --version
R scripting front-end version 4.0.3 (2020-10-10)

To disable (“unload”) R, that is, remove it from the search path, do:

module unload r

To see what software modules you have currently loaded, use:

module list

To disable all loaded software modules and repositories, use:

module purge

To see what software modules are currently available (in the software repositories you have loaded), use:

module avail

or alternative,

module spider

If the software repository provides more than one version of each software, specific versions can be loaded using the module load <software>/<version> format. For instance, the CBI repository provides a large number of historical R versions. To load R 3.2.0, use:

module load r/3.2.0

Comment: If another version of R is already loaded, that will automatically be unloaded before loading the new version.

Using within a login shell #

Since module is only available on the development and compute nodes, its use in a login script (.profile, .bash_profile, .bashrc), we can only call it where its supported. It is supported when environment variable MODULEPATH is set. The below ~/.bashrc code snippet shows how to check for this. Moreover, many of the modules provide software tools that are only useful in interactive mode on a development node. The below example shows how to load modules only when running in interactive mode.

## Are environment modules supported?
if [[ -n "$MODULEPATH" ]]; then
    ## Load modules for interactive use
    ## (these will not be loaded when running jobs)
    if [[ $- == *i* ]]; then
        module load CBI htop mc 
    fi
fi

See also #

For more information on how to use modules and the module command, see module --help, man module, and the official Lmod documentation.

Technical details #

Instead of the classical Tcl-based environment module system commonly available on Linux, the cluster uses a Lua-based environment module system called Lmod. Lmod has a several advantages over the Tcl-based module system while being backward compatible, i.e. users of Tcl modules can still use them with Lmod. There are a few rare corner cases where a Tcl module might fail and the module has to be rewritten as a Lua-based module.

When loading a software repository (module load <repos>), it will append its module folder to the $MODULEPATH. Unloading it (module unload <repos>) will undo any changes. For instance, module load <repos> appends $MODULEPATH_ROOT/<repos> to your $MODULEPATH. Multiple software repositories can be loaded in one call, e.g. module load <repos1> <repos2>. It is also possible to load a software repository and some of its software tools in one call, e.g. module load <repos> <software1> <software2>.