Module Commands in an LSF 10.1 Environment
Note: In the following descriptions, the combined symbols “$>” are used as a stand-in for a LINUX terminal command prompt.
The LSF Job Scheduler in the CAD Compute Cluster runs constantly, and never has to be started. It has been configured with certain queues that handle requests for cores and memory. Any command prefaced by the letters “ls” or “b” is interpreted as a request for information about the cluster and its environment or set-up. For example, the command:
… will list the names of all nodes in the cluster with their static resources (cores and memory, plus other information). The command:
… will display the available queues for batch operation with assigned levels of priority, or ‘niceness’.
When logging into the CAD Compute Cluster, a user will be in a standard LINUX environment with a default ‘bash’ shell. This is a basic operating environment. More information about the bash shell is given here:
… in the tutorials section.
The LSF commands shown here are variations on the “module…” key word. A complete list of these variations is available in a terminal window by typing
$> module –help
The generic command structure is:
Usage: module [ switches ] [ subcommand ] [ subcommand – arguments ]
Discovering the CAD System Contents/Loaded Software
$> module list
Reports which module files are currently loaded in the environment.
$> module avail
Reports which tools and software are have been installed under the directories:
/usr/share/Modules/modulefiles <– bundled with the job scheduler
/CMC/modules/ <– CAD tools installed by CMC Microsystems’ administrators
Installing CAD Tools before a Simulation Run
$> module load <tool name>
Adds a module to the user’s current environment. Only applies to the terminal window in which it is called.
$> module unload <tool name>
Removes a module from the user’s current environment.
$> module switch <loaded tool name> <replacement tool name>
Swaps modules as directed by the subcommands.
Information about the Modules
$> module whatis <subcommand>
Finds more detail about the specified module.
$> module show/display <tool name>
Finds PATH and environment variables for a particular module or tool name.