Skip to main content

Software Environment

TL;DR

If you need something that is not there please submit your request to get it installed.

Modules​

The module package provides a dynamic modification of a user's environment. The software administrator defines the module and the user loads it.

Modules can be invoked in two ways: by name alone or by name and version. Invoking them by name implies loading the default module version. This is usually the most recent version that has been tested to be stable (recommended) or the only version available.

[ user@hpc ~]$ module load torch

Invoking by version loads the version specified of the application. As of this writing, the previous command and the following one load the same module.

[ user@hpc ~]$ module load torch/2.3.1

The most important commands for modules are these:

  • module list: shows all the loaded modules
  • module avail: shows all the modules the user is able to load
  • module purge: removes all the loaded modules
  • module load <modulename>: loads the necessary environment variables for the selected modulefile (PATH, MANPATH, LD_LIBRARY_PATH...)
  • module unload <modulename>: removes all environment changes made by module load command
  • module switch <oldmodule> <newmodule>: unloads the first module (oldmodule) and loads the second module (newmodule)

You can run module help any time to check the command's usage and options or check the module(1) manpage for further information.