Modules - Revision history

Ianc: /* GNU Modules */

2026-03-08T23:07:34Z

GNU Modules

← Older revision		Revision as of 23:07, 8 March 2026
Line 2:		Line 2:
	Many large institutions use the concept of Modules to load software into user environments. They provide a way to add and remove environmental variables that provide access to UMIACS' large set of software that we offer on our [[RHEL \| Red Hat Enterprise Linux (RHEL)]] and [[Ubuntu]] platforms. They work by customizing your shell environment which is done automatically for the two major shell families (bash/sh (default shell) and tcsh/csh). If you use an alternate shell, please look to source the appropriate script for your shell in <tt>/usr/share/Modules/init</tt>.		Many large institutions use the concept of Modules to load software into user environments. They provide a way to add and remove environmental variables that provide access to UMIACS' large set of software that we offer on our [[RHEL \| Red Hat Enterprise Linux (RHEL)]] and [[Ubuntu]] platforms. They work by customizing your shell environment which is done automatically for the two major shell families (bash/sh (default shell) and tcsh/csh). If you use an alternate shell, please look to source the appropriate script for your shell in <tt>/usr/share/Modules/init</tt>.

	Initially your module environment is empty, though included in your module path are local operating system specific modules, locally built software modules, and binary software modules (Matlab, Intel Compiler, etc.).		Initially your module environment is empty, though included in your module path are local operating system specific modules, locally built software modules, and binary software modules ([[Matlab]], Intel Compiler, etc.).

	==Available Software==		==Available Software==

Mbaney at 15:56, 20 November 2024

2024-11-20T15:56:51Z

← Older revision		Revision as of 15:56, 20 November 2024
Line 91:		Line 91:
	In non-interactive shell sessions (non-login shells), the Modules configuration environment will not automatically load. This will also occur if the OS version of the compute node you are scheduled on is different from the OS version of the submission node you are submitting the job from.		In non-interactive shell sessions (non-login shells), the Modules configuration environment will not automatically load. This will also occur if the OS version of the compute node you are scheduled on is different from the OS version of the submission node you are submitting the job from.

	If you will need the use of Modules in non-interactive [[SLURM]] jobs, cross-OS jobs, or other similar sessions, you will need to include the following in your shell init scripts:		If you will need the use of Modules in non-interactive [[SLURM]] jobs, cross-OS jobs, or other similar sessions, you will need to include the following in your shell init scripts. For [[SLURM]] specifically, please ensure you include these statements after any #SBATCH directives in your submission batch scripts, otherwise these directives will not work.

	===Bash===		===Bash===

Mbaney at 13:39, 23 October 2024

2024-10-23T13:39:50Z

← Older revision		Revision as of 13:39, 23 October 2024
Line 1:		Line 1:
	=GNU Modules=		=GNU Modules=
	Many large institutions use the concept of Modules to load software into user environments. They provide a way to add and remove environmental variables that provide access to UMIACS' large set of software that we offer on our Red Hat Enterprise Linux (RHEL) and [[Ubuntu]] platforms. They work by customizing your shell environment which is done automatically for the two major shell families (bash/sh (default shell) and tcsh/csh). If you use an alternate shell, please look to source the appropriate script for your shell in <tt>/usr/share/Modules/init</tt>.		Many large institutions use the concept of Modules to load software into user environments. They provide a way to add and remove environmental variables that provide access to UMIACS' large set of software that we offer on our [[RHEL \| Red Hat Enterprise Linux (RHEL)]] and [[Ubuntu]] platforms. They work by customizing your shell environment which is done automatically for the two major shell families (bash/sh (default shell) and tcsh/csh). If you use an alternate shell, please look to source the appropriate script for your shell in <tt>/usr/share/Modules/init</tt>.

	Initially your module environment is empty, though included in your module path are local operating system specific modules, locally built software modules, and binary software modules (Matlab, Intel Compiler, etc.).		Initially your module environment is empty, though included in your module path are local operating system specific modules, locally built software modules, and binary software modules (Matlab, Intel Compiler, etc.).

Mbaney at 13:35, 23 October 2024

2024-10-23T13:35:39Z

← Older revision		Revision as of 13:35, 23 October 2024
Line 1:		Line 1:
	=GNU Modules=		=GNU Modules=
	Many large institutions use the concept of Modules to load software into user environments. They provide a way to add and remove environmental variables that provide access to UMIACS' large set of software that we offer on our Red Hat Enterprise Linux (~~[[RedHat]]~~) and [[Ubuntu]] platforms. They work by customizing your shell environment which is done automatically for the two major shell families (bash/sh (default shell) and tcsh/csh). If you use an alternate shell, please look to source the appropriate script for your shell in <tt>/usr/share/Modules/init</tt>.		Many large institutions use the concept of Modules to load software into user environments. They provide a way to add and remove environmental variables that provide access to UMIACS' large set of software that we offer on our Red Hat Enterprise Linux (RHEL) and [[Ubuntu]] platforms. They work by customizing your shell environment which is done automatically for the two major shell families (bash/sh (default shell) and tcsh/csh). If you use an alternate shell, please look to source the appropriate script for your shell in <tt>/usr/share/Modules/init</tt>.

	Initially your module environment is empty, though included in your module path are local operating system specific modules, locally built software modules, and binary software modules (Matlab, Intel Compiler, etc.).		Initially your module environment is empty, though included in your module path are local operating system specific modules, locally built software modules, and binary software modules (Matlab, Intel Compiler, etc.).

Seide: RHEL9 desktop node

2024-09-12T17:40:30Z

RHEL9 desktop node

← Older revision		Revision as of 17:40, 12 September 2024
Line 104:		Line 104:
	source /etc/profile.d/ummodules.csh		source /etc/profile.d/ummodules.csh
	</pre>		</pre>

			==Modules on RHEL9 Desktop Sessions==
			Because of changes made in GNOME between RHEL8 and RHEL9, the <tt>module</tt> command will not work on desktop sessions out of the box. In order to use modules in a shell opened from a desktop session, you must source the modules init script. See [[#Modules in Non-Interactive Shell Sessions]] for the required commands. For convenience, we recommend adding this to the top of your shell init file (e.g ~/.bashrc, ~/.tcshrc), this way it gets sourced automatically with each new shell.

			Note that this issue does not affect RHEL9 SSH sessions, only sessions using the desktop GUI.

	==Additional Help==		==Additional Help==

Mbaney at 17:55, 10 July 2024

2024-07-10T17:55:01Z

← Older revision		Revision as of 17:55, 10 July 2024
Line 27:		Line 27:
	</pre>		</pre>

	~~There~~ may ~~be a~~ (default) module ~~otherwise~~ the most recent version of ~~software is loaded when specified~~.		Some pieces of software may have default versions that are loaded if no version is explicitly specified, indicated by <code>(default)</code> coming after their name/version in the output of <tt>module avail</tt>. If a piece of software does not have any default version and you load it without specifying a version, you will load the most recent version of it.

	==Adding Modules into your Environment==		==Adding Modules into your Environment==
Line 39:		Line 39:

	<pre>		<pre>
	[username@nexusstaff00 ~]$ module add Python3/3.11.2		[username@nexusstaff00 ~]$ module add Python3/3.10.10
	</pre>		</pre>

Line 48:		Line 48:
	[username@nexusstaff00 ~]$ module list		[username@nexusstaff00 ~]$ module list
	Currently Loaded Modulefiles:		Currently Loaded Modulefiles:
	1) Python3/3.11.2 2) cuda/12.1.1		1) Python3/3.10.10 2) cuda/12.1.1
	</pre>		</pre>

Mbaney: /* Showing a Module */

2024-03-01T17:55:20Z

Showing a Module

Mbaney: /* Listing Modules */

2024-03-01T17:54:32Z

Listing Modules

← Older revision		Revision as of 17:54, 1 March 2024
Line 48:		Line 48:
	[username@nexusstaff00 ~]$ module list		[username@nexusstaff00 ~]$ module list
	Currently Loaded Modulefiles:		Currently Loaded Modulefiles:
	1) ~~cuda~~/10.2~~.89(default)~~ 2) ~~Python3~~/3.11.2		1) Python3/3.11.2 2) cuda/12.1.1
	</pre>		</pre>

Mbaney: /* Available Software */

2024-03-01T17:52:55Z

Available Software

← Older revision		Revision as of 17:52, 1 March 2024
Line 12:		Line 12:
	cuda/3.2.16 cuda/6.5.14 cuda/9.0.176 cuda/11.0.3 cuda/11.8.0		cuda/3.2.16 cuda/6.5.14 cuda/9.0.176 cuda/11.0.3 cuda/11.8.0
	cuda/4.2.9 cuda/7.0.28 cuda/9.1.85 cuda/11.1.1 cuda/12.0.1		cuda/4.2.9 cuda/7.0.28 cuda/9.1.85 cuda/11.1.1 cuda/12.0.1
	cuda/5.0.35 cuda/7.5.18 cuda/9.2.148 cuda/11.2.2 cuda/12.1.1~~(default)~~		cuda/5.0.35 cuda/7.5.18 cuda/9.2.148 cuda/11.2.2 cuda/12.1.1
	cuda/5.5.11 cuda/8.0.27rc2 cuda/10.0.130 cuda/11.3.1		cuda/5.5.11 cuda/8.0.27rc2 cuda/10.0.130 cuda/11.3.1
	cuda/5.5.22 cuda/8.0.44 cuda/10.1.243 cuda/11.4.4		cuda/5.5.22 cuda/8.0.44 cuda/10.1.243 cuda/11.4.4

Mbaney: /* Available Software */

2024-03-01T17:51:34Z

Available Software

← Older revision		Revision as of 17:51, 1 March 2024
Line 10:		Line 10:
	[username@nexusstaff00 ~]$ module avail cuda		[username@nexusstaff00 ~]$ module avail cuda
	--------------------------- /opt/common/.modulefiles ---------------------------		--------------------------- /opt/common/.modulefiles ---------------------------
	cuda/3.2.16 cuda/6.5.14 cuda/9.0.176 cuda/11.0.3 cuda/11.8.0		cuda/3.2.16 cuda/6.5.14 cuda/9.0.176 cuda/11.0.3 cuda/11.8.0
	cuda/4.2.9 cuda/7.0.28 cuda/9.1.85 cuda/11.1.1 cuda/12.0.1		cuda/4.2.9 cuda/7.0.28 cuda/9.1.85 cuda/11.1.1 cuda/12.0.1
	cuda/5.0.35 cuda/7.5.18 cuda/9.2.148 cuda/11.2.2		cuda/5.0.35 cuda/7.5.18 cuda/9.2.148 cuda/11.2.2 cuda/12.1.1(default)
	cuda/5.5.11 cuda/8.0.27rc2 cuda/10.0.130 cuda/11.3.1		cuda/5.5.11 cuda/8.0.27rc2 cuda/10.0.130 cuda/11.3.1
	cuda/5.5.22 cuda/8.0.44 cuda/10.1.243 cuda/11.4.4		cuda/5.5.22 cuda/8.0.44 cuda/10.1.243 cuda/11.4.4
	cuda/6.0.37 cuda/8.0.61 cuda/10.2.89~~(default)~~ cuda/11.7.0		cuda/6.0.37 cuda/8.0.61 cuda/10.2.89 cuda/11.7.0
	</pre>		</pre>

← Older revision		Revision as of 17:55, 1 March 2024
Line 57:		Line 57:
	[username@nexusstaff00 ~]$ module show cuda		[username@nexusstaff00 ~]$ module show cuda
	-------------------------------------------------------------------		-------------------------------------------------------------------
	/opt/common/.modulefiles/cuda/10.2.89:		/opt/common/.modulefiles/cuda/12.1.1:

	conflict cuda/10.1.243 cuda/10.0.130 cuda/9.2.148 cuda/9.1.85 cuda/9.0.176 cuda/8.0.61 cuda/8.0.44 cuda/8.0.27rc2 cuda/7.5.18 cuda/7.0.28 cuda/6.5.14 cuda/6.0.37 cuda/5.5.22 cuda/5.5.11 cuda/5.0.35 cuda/4.2.9 cuda/3.2.16		conflict cuda/12.0.1 cuda/11.8.0 cuda/11.7.0 cuda/11.4.4 cuda/11.2.2 cuda/11.1.1 cuda/11.0.3 cuda/10.2.89 cuda/10.1.243 cuda/10.0.130 cuda/9.2.148 cuda/9.1.85 cuda/9.0.176 cuda/8.0.61 cuda/8.0.44 cuda/8.0.27rc2 cuda/7.5.18 cuda/7.0.28 cuda/6.5.14 cuda/6.0.37 cuda/5.5.22 cuda/5.5.11 cuda/5.0.35 cuda/4.2.9 cuda/3.2.16
	prepend-path PATH /opt/common/cuda/cuda-10.2.89/bin		prepend-path PATH /opt/common/cuda/cuda-12.1.1/bin
	prepend-path LD_LIBRARY_PATH /opt/common/cuda/cuda-10.2.89/lib64		prepend-path LD_LIBRARY_PATH /opt/common/cuda/cuda-12.1.1/lib64
	prepend-path LD_RUN_PATH /usr/lib64/nvidia:/usr/lib/nvidia:/opt/common/cuda/cuda-10.2.89/lib64:/opt/common/cuda/cuda-10.2.89/lib		prepend-path LD_RUN_PATH /usr/lib64/nvidia:/usr/lib/nvidia:/opt/common/cuda/cuda-12.1.1/lib64:/opt/common/cuda/cuda-12.1.1/lib
	prepend-path LIBRARY_PATH /usr/lib64/nvidia:/usr/lib/nvidia:/opt/common/cuda/cuda-10.2.89/lib64:/opt/common/cuda/cuda-10.2.89/lib		prepend-path LIBRARY_PATH /usr/lib64/nvidia:/usr/lib/nvidia:/opt/common/cuda/cuda-12.1.1/lib64:/opt/common/cuda/cuda-12.1.1/lib
	prepend-path CPATH /opt/common/cuda/cuda-10.2.89/include		prepend-path CPATH /opt/common/cuda/cuda-12.1.1/include
	prepend-path PKG_CONFIG_PATH /opt/common/cuda/cuda-10.2.89/pkgconfig		prepend-path PKG_CONFIG_PATH /opt/common/cuda/cuda-12.1.1/pkgconfig
	setenv CUDA_HOME /opt/common/cuda/cuda-10.2.89		setenv CUDA_HOME /opt/common/cuda/cuda-12.1.1
	-------------------------------------------------------------------		-------------------------------------------------------------------
	</pre>		</pre>