The Module Command

Software installations on the clusters span many applications, and many different version numbers of the same application. It is not possible (nor desirable) to use them all at the same time, since different versions of the same application may conflict with each other. In order to simplify the control of which application versions are available in a specific session, there is a system for loading and unloading 'modules' which activate and deactivate the relevant parts of your user session.

Which modules are loaded?

To see the modules currently active in your session, use the command

module list

If nothing else has been explicitly activated, the result will be the default setting of two modules: mpi and intelcomp. (These activate the default MPI library and the Intel compiler suite.)

Which modules are available?

In order to see a complete list of available modules, issue the command

module avail

The resulting list will contain module names conforming to the following pattern:

• Capitalized names represent specific application versions, and look like Name.version
• Non-capitalized names are without version numbering, and represent the most recent and tested version of the module

The purpose of this is to make upgrades transparent to the user; the lowercase module name will load the most recent working module even if the software has been upgraded since last time the command was used. This relieves the user of constantly tracking version numbers and updating scripts to match them.

How are modules loaded?

In order to enable, for instance, the GLView software, issue the command

module load glview

The commands which belong to GLView (e.g. 'xglview') can then be used in your session.

How are modules unloaded?

Keeping with the above example, use the following command to unload the GLView module again:

module unload glview

Which version of a module is the default?

$ module avail
...
adf/2005.01b                 ncarg/5.0.0
adf/2006.01b                 nco/3.1.8(default)
adf/2006.01d(default)        nco/3.9.1
adf/2007.01                  nedit/5.5(default)

By typing «module load adf», you will load the default adf version, version 2006.01d. To run another version than the default, say the more recent version 2007.1, you have to specify this with an explicit version load:

module load adf/2007.01

How do I switch to a different version of a module?

Switching to another version is similar to loading a specific version. As an example, if you want to switch from the default (current) Intel compilers version to version 8.0, type

module switch intelcomp intelcomp/8.0