The Environment Module approach has been adopted to help simplify the complex software requirements on UNT HPC systems. Talon supports numerous software packages, libraries, and compilers. The Modules package provides a powerful command driven interface for modifying environments in order to run certain calucations. This abstraction allows users to instantaneously modify software paths, library paths and other variables by 'load'ing and 'unload'ing different modules.
The following table lists frequently used commands:
|module avail||List all modules currently available.|
|module list||List all modules currently loaded into environment.|
|module help application||Print Module specific help for application application. Without the application argument, module command usage will be displayed.|
|module load application||Load all settings for application into current environment.|
|module unload application||Unload all settings for application in current environment.|
|module initadd application||Add application to the shell’s initialization file in the user’s home directory.|
|module help application||Details information about the application|
Often, there is more than one version of a module available. This normally means that one is set as the default version by administrators. This require the user to recognize this and if the default is not the desired version add the correct version to start up files via the module initadd application/X.X command
In an effort to help ensure module use is as simple as possible, the modules have been organized into classes. The following table details the class structure:
|scientific||end-user scientific applications|
tools to assist with debugging, development, and tuning tasks. This has available compilers, libraries and MPI environments.
List modules currently available
Loading a module:
*where module_name is the name of the module to be loaded (ex. fftw, matlab, gaussian, etc.)
Unloading a module
*Note: this is done silently.
List modules currently loaded in your environment