|
Environment Modules provides an easy mechanism for setting up a user's environment for a particular application. The module command is functionally equivalent, irrespective of the shell you are using.
Prior to using the module command, the Module software must be initialized. In your HPCCC account, your dot-files are already set up correctly to do this.
If, for any reason the module command is unavailable, you must manually initialize modules in your script before using the module utility. For example, if you run batch jobs with /bin/sh you will need to initialize modules manually. Choose the appropriate initialization command for your host and script environment from those shown below.
flurry, gale
solar
cherax, burnet
Modules uses a quite sophisticated model for tracking environment settings and allow loading, unloading and switching of modules, including specification of dependencies and conflicts in the module definitions. A range of commands are available to query the current environment and the available modules. In summary:
Note: If there is a default version for a software package, it will be shown in the output of module avail as '(default)' listed next to the package name. If the revision number is omitted for a module load when there is no default, the latest version will be loaded.
Other information on modules can be found by reading the man pages man module, but you will need to run module load modules first.
The Modules sources can be found at the following Sourceforge site (http://modules.sourceforge.net/), which also requires the Tcl sources (http://www.scriptics.com/).