Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Note:  It is possible to have two or more versions of the same module loaded, but this can cause problems and should be avoided.  The reason for this is often that a major version change in software can result in significantly different syntax, so software developers maintain multiple, independent streams of their software.  All aliases defined above can be considered examples of this.



Listing available software and versions

No Format
module avail

Information about a piece of software (example)

No Format
module help grass

Listing environment modules you have loaded.

No Format
module list

Unloading all modules

There will be occasions where it is easier to make a fresh start, in which case you simply run the command

No Format
module purge


Loading a specific software version (example)

No Format
module load gcc/6

Loading the default version of a piece of software (example)

No Format
module load java

NOTE:  The default software version will generally be the safest (e.g., version distributed by RedHat).

An example of a command to switch to another version of the same software is:

No Format
module switch java/1.6.0-openjdk

Unloading a module (example)

No Format
module unload java

In some cases, you may want/need to add the version.


Information specific to JCU HPC configuration

Most module files, when loaded, will set an environment variable <SOFTWARE>_HOME which holds the installation home for the software.  For example, try