This is Lite Plone Theme
You are here: Home Developer Guide Modules


Basics of using the module command to manage your paths and library paths to available applications and libraries available on COSMOS systems.

Most of the development software on COSMOS presented here has a module interface. That is,  it either exists in a number of incompatible versions, or uses non-standard paths in the directory hierarchy, and access to it is not enabled by default. The interface to different packages is managed via environmental modules. This makes it easier to maintain several versions of the same software avoiding interference between similar components. To access a particular software package or library with a module interface you should first load the corresponding module using:

$ module load full-module-name

This will set up the necessary environmental variables and paths required by the package. You can load as many modules as you require in a session, but be aware that if you load multiple modules with overlapping components (e.g.. two different versions of the same compiler) the module loaded last will have precedence. In order to avoid confusion you can unload a module once it is no longer needed by typing:

$ module unload full-module-name

There are various commands available to manage modules. Among the most useful ones are:

$ module list

To see all the modules that you have currently loaded. And:

$ module avail

To see a list of all the modules available on COSMOS.

Use 'module -help' for a complete list of commands. The default developer environment on COSMOS is based around the Intel Compilers.