Goal: Provide a summary of concepts and commands covered.

Module Commands Covered

Typing module from the command-line will list all the available sub-commands.

Sub-command	Description

Sub-command	Description
`spider <module-name>`	Search for versions of the module called `<module-name>`.
`spider <module-name>/<version>`	Find details, including required dependencies, for a specific `<version>` of a `<module-name>`.
`load <module-name>/<version>`	Load the specific `<module-name>` with `<version>`.
`list`	List the modules, and their dependencies, that you currently have loaded. The short cut to this is `ml`.
`avail`	List the various modules that are available to load with respect to what you already have loaded.
`purge`	Reset your environment, unloading anything that you have previously loaded. The ARCC related `slurm` and `arcc` modules will remain loaded.

Summary

Looked at:

How to set up various environments, using the LMOD module system, to allow you to personalize the use of a variety of programming languages, applications, libraries and utilities. This included:
- how to search to see if modules are available: module spider.
- how to load a module: module load.
- resetting your environment using module purge.
- listing what you currently have available using module list and/or ml.
Modules are grouped depending on how they’ve been installed by ARCC.
- Anything that needed to be compiled lives under a compiler tree, and potentially an mpi related dependency.
Only one compiler can be loaded within a session at a time.
Modules can have 10s of dependencies that are loaded behind the scene.
Different sessions are independent from each other and can have different modules loaded.

Prev

Required Software is Not Available

Workshop Home

Intro to using the Module System

Use the following link to provide feedback on this training: Module System Training Evaluation or use the QR code below.