Jump to: navigation, search


The default shell for all users is bash. GNU bash.

Home Directories

HPC Host Home directory
Cnrdp.arcs AFS
Kong local
Gorgon AFS
Stheno local


The Environment Modules package provides for the dynamic modification of a user's environment via modulefiles.

Each modulefile contains the information needed to configure the shell for an application. Once the Modules package is initialized, the environment can be modified on a per-module basis using the module command which interprets modulefiles. Typically modulefiles instruct the module command to alter or set shell environment variables such as PATH, MANPATH, etc. modulefiles may be shared by many users on a system and users may have their own collection to supplement or replace the shared modulefiles. Modules

Command Description Example
module available (av) lists available modules module av
module available string lists available modules matching string module av gcc
module load modulefile loads modulefile module load gcc
module list lists currently loaded modules module list
module unload modulefile unloads modulefile module unload gcc
module switch modulefile loads different version of currently loaded module file module load gcc5/5.2.0
module switch gcc5/5.3.0
module purge unloads all loaded modules. Restores environment to state
before any modules were loaded
module purge

"man module", or view the manpage online.

All of the applications listed on the Applications page have an associated module file. This module file must be loaded to set the user environment for the application. If you frequently use a particular application it is convenient to load the module every login. This can easily be done by adding the module command in your ~/.bashrc file - i.e., "module load application".

Modules in submit scripts

If a module is needed to run a command on a compute node, include the following just before the command :

. /opt/Modules/init/bash
module load <modulefile>