NEMO2/Easybuild Modules - Revision history

M Janczyk: /* Physical vs. Symbolic Architectures */

2026-06-16T15:16:17Z

Physical vs. Symbolic Architectures

← Older revision		Revision as of 17:16, 16 June 2026
Line 50:		Line 50:
	\| <code>h200</code> \|\| AMD Genoa CPUs + NVIDIA H200 GPUs \|\| '''Symbolic link → genoa''' \|\| Uses genoa installation directory		\| <code>h200</code> \|\| AMD Genoa CPUs + NVIDIA H200 GPUs \|\| '''Symbolic link → genoa''' \|\| Uses genoa installation directory
	\|-		\|-
	\| <code>rtx</code> \|\| AMD Genoa CPUs + NVIDIA RTX PRO 6000 Blackwell GPUs \|\| '''Symbolic link → ~~h200~~''' \|\| Uses ~~h200~~ installation directory		\| <code>rtx</code> \|\| AMD Genoa CPUs + NVIDIA RTX PRO 6000 Blackwell GPUs \|\| '''Symbolic link → genoa''' \|\| Uses genoa installation directory
	\|}		\|}

Line 63:		Line 63:
	* <code>~/.local/easybuild/rtx/</code>		* <code>~/.local/easybuild/rtx/</code>

	'''Optional:''' You can manually create symbolic links (<code>mi300a → genoa</code>, <code>h200 → genoa</code>, <code>rtx → ~~h200~~</code>) to mirror the global structure, but this is not required. See [[NEMO2/Easybuild_Modules/EB_Build_Module#Architecture_Support\|Architecture Support]] for details.		'''Optional:''' You can manually create symbolic links (<code>mi300a → genoa</code>, <code>h200 → genoa</code>, <code>rtx → genoa</code>) to mirror the global structure, but this is not required. See [[NEMO2/Easybuild_Modules/EB_Build_Module#Architecture_Support\|Architecture Support]] for details.

	== Viewing Modules for Specific Architectures ==		== Viewing Modules for Specific Architectures ==

M Janczyk: /* Physical vs. Symbolic Architectures */

2026-06-16T15:13:58Z

Physical vs. Symbolic Architectures

← Older revision		Revision as of 17:13, 16 June 2026
Line 49:		Line 49:
	\|-		\|-
	\| <code>h200</code> \|\| AMD Genoa CPUs + NVIDIA H200 GPUs \|\| '''Symbolic link → genoa''' \|\| Uses genoa installation directory		\| <code>h200</code> \|\| AMD Genoa CPUs + NVIDIA H200 GPUs \|\| '''Symbolic link → genoa''' \|\| Uses genoa installation directory
			\|-
			\| <code>rtx</code> \|\| AMD Genoa CPUs + NVIDIA RTX PRO 6000 Blackwell GPUs \|\| '''Symbolic link → h200''' \|\| Uses h200 installation directory
	\|}		\|}

	'''What this means for system modules (<code>/opt/eb</code>):''' The global NEMO2 modules use symbolic links, so modules for <code>mi300a</code> and <code>~~h200~~</code> are actually stored in the <code>genoa</code> directory. This is because these GPU nodes use AMD Genoa CPUs as their host processors.		'''What this means for system modules (<code>/opt/eb</code>):''' The global NEMO2 modules use symbolic links, so modules for <code>mi300a</code>, <code>h200</code> and <code>rtx</code> are actually stored in the <code>genoa</code> directory. This is because these GPU nodes use AMD Genoa CPUs as their host processors.

	'''What this means for self-built modules:''' When you build your own modules with <code>eb-build-module.sh</code>, each architecture gets its own separate directory by default:		'''What this means for self-built modules:''' When you build your own modules with <code>eb-build-module.sh</code>, each architecture gets its own separate directory by default:
Line 59:		Line 61:
	* <code>~/.local/easybuild/l40s/</code>		* <code>~/.local/easybuild/l40s/</code>
	* <code>~/.local/easybuild/h200/</code>		* <code>~/.local/easybuild/h200/</code>
			* <code>~/.local/easybuild/rtx/</code>

	'''Optional:''' You can manually create symbolic links (<code>mi300a → genoa</code>, <code>h200 → genoa</code>) to mirror the global structure, but this is not required. See [[NEMO2/Easybuild_Modules/EB_Build_Module#Architecture_Support\|Architecture Support]] for details.		'''Optional:''' You can manually create symbolic links (<code>mi300a → genoa</code>, <code>h200 → genoa</code>, <code>rtx → h200</code>) to mirror the global structure, but this is not required. See [[NEMO2/Easybuild_Modules/EB_Build_Module#Architecture_Support\|Architecture Support]] for details.

	== Viewing Modules for Specific Architectures ==		== Viewing Modules for Specific Architectures ==

M Janczyk: /* Available Architecture Modules */

2026-06-16T15:11:35Z

Available Architecture Modules

← Older revision		Revision as of 17:11, 16 June 2026
Line 30:		Line 30:
	* <code>arch/l40s</code> - NVIDIA L40S GPUs (Intel-based nodes)		* <code>arch/l40s</code> - NVIDIA L40S GPUs (Intel-based nodes)
	* <code>arch/h200</code> - NVIDIA H200 GPUs		* <code>arch/h200</code> - NVIDIA H200 GPUs
			* <code>arch/rtx</code> - NVIDIA RTX PRO 6000 Blackwell GPUs

	== Physical vs. Symbolic Architectures ==		== Physical vs. Symbolic Architectures ==

M Janczyk at 14:43, 11 June 2026

2026-06-11T14:43:03Z

← Older revision		Revision as of 16:43, 11 June 2026
Line 73:		Line 73:
	</syntaxhighlight>		</syntaxhighlight>

	The <code>$~~ARCH~~</code> environment variable is automatically set when you load an architecture:		The <code>$MODULE_ARCH</code> environment variable is automatically set when you load an architecture:
	<syntaxhighlight lang="bash">		<syntaxhighlight lang="bash">
	module load arch/genoa		module load arch/genoa
	echo $~~ARCH~~ # Output: genoa		echo $MODULE_ARCH # Output: genoa
	</syntaxhighlight>		</syntaxhighlight>

Line 244:		Line 244:
	= Compiling Your Own Software (Non-EasyBuild) =		= Compiling Your Own Software (Non-EasyBuild) =

	If you compile your own applications outside of EasyBuild (e.g., custom C/C++/Fortran code), you should create architecture-specific builds using the <code>$~~ARCH~~</code> environment variable.		If you compile your own applications outside of EasyBuild (e.g., custom C/C++/Fortran code), you should create architecture-specific builds using the <code>$MODULE_ARCH</code> environment variable.

	== Using $~~ARCH~~ in Your Workflows ==		== Using $MODULE_ARCH in Your Workflows ==

	The <code>$~~ARCH~~</code> variable is automatically set when you load an architecture module:		The <code>$MODULE_ARCH</code> variable is automatically set when you load an architecture module:

	<syntaxhighlight lang="bash">		<syntaxhighlight lang="bash">
	module load arch/milan		module load arch/milan
	echo $~~ARCH~~ # Output: milan		echo $MODULE_ARCH # Output: milan
	</syntaxhighlight>		</syntaxhighlight>

Line 258:		Line 258:
	<syntaxhighlight lang="bash">		<syntaxhighlight lang="bash">
	# Organize binaries by architecture		# Organize binaries by architecture
	$HOME/software/$~~ARCH~~/myapp/bin/myprogram		$HOME/software/$MODULE_ARCH/myapp/bin/myprogram

	# Example paths for different architectures:		# Example paths for different architectures:
Line 271:		Line 271:
	# Compile for Milan		# Compile for Milan
	module load arch/milan		module load arch/milan
	gcc -O3 -march=znver3 mycode.c -o $HOME/software/$~~ARCH~~/bin/myprogram		gcc -O3 -march=znver3 mycode.c -o $HOME/software/$MODULE_ARCH/bin/myprogram

	# Compile for Genoa		# Compile for Genoa
	module load arch/genoa		module load arch/genoa
	gcc -O3 -march=znver4 mycode.c -o $HOME/software/$~~ARCH~~/bin/myprogram		gcc -O3 -march=znver4 mycode.c -o $HOME/software/$MODULE_ARCH/bin/myprogram
	</syntaxhighlight>		</syntaxhighlight>

M Janczyk at 15:26, 24 November 2025

2025-11-24T15:26:27Z

← Older revision		Revision as of 17:26, 24 November 2025
Line 90:		Line 90:
	When in doubt, build separate versions for each architecture you plan to use.		When in doubt, build separate versions for each architecture you plan to use.

	== Building Your Own EasyBuild Modules ==		= Building Your Own EasyBuild Modules =

	If you need software that is not yet available as a module on NEMO2, you can build your own EasyBuild modules. NEMO2 provides the <code>eb-build-module.sh</code> script that makes this process straightforward.		If you need software that is not yet available as a module on NEMO2, you can build your own EasyBuild modules. NEMO2 provides the <code>eb-build-module.sh</code> script that makes this process straightforward.
Line 242:		Line 242:
	* '''Available easyconfigs:''' Use <code>eb-build-module.sh -s pattern</code> to search		* '''Available easyconfigs:''' Use <code>eb-build-module.sh -s pattern</code> to search

	== Compiling Your Own Software (Non-EasyBuild) ==		= Compiling Your Own Software (Non-EasyBuild) =

	If you compile your own applications outside of EasyBuild (e.g., custom C/C++/Fortran code), you should create architecture-specific builds using the <code>$ARCH</code> environment variable.		If you compile your own applications outside of EasyBuild (e.g., custom C/C++/Fortran code), you should create architecture-specific builds using the <code>$ARCH</code> environment variable.

M Janczyk at 15:22, 24 November 2025

2025-11-24T15:22:56Z

Show changes

M Janczyk at 14:49, 24 November 2025

2025-11-24T14:49:10Z

M Janczyk at 14:46, 24 November 2025

2025-11-24T14:46:38Z

Show changes

M Janczyk at 17:49, 10 October 2025

2025-10-10T17:49:23Z

← Older revision		Revision as of 19:49, 10 October 2025
Line 7:		Line 7:
	* GitHub repository: https://github.com/easybuilders/easybuild		* GitHub repository: https://github.com/easybuilders/easybuild
	* Documentation: https://docs.easybuild.io/		* Documentation: https://docs.easybuild.io/

			'''For available EasyBuild modules, you currently need to visit the [https://www.nemo.uni-freiburg.de/easybuild-modules/ NEMO website].'''

M Janczyk at 16:58, 5 June 2025

2025-06-05T16:58:16Z

← Older revision		Revision as of 18:58, 5 June 2025
Line 7:		Line 7:
	* GitHub repository: https://github.com/easybuilders/easybuild		* GitHub repository: https://github.com/easybuilders/easybuild
	* Documentation: https://docs.easybuild.io/		* Documentation: https://docs.easybuild.io/


			__TOC__

	== Modules for Each Architecture and Slurm Partition ==		== Modules for Each Architecture and Slurm Partition ==
Line 33:		Line 36:

	Loading a new architecture module with <code>module load arch/<arch></code> sets the environment variable <code>ARCH=<arch></code>. This is done automatically on each node. If you want to override it, you must run </code>module load arch/<arch></code> explicitly.		Loading a new architecture module with <code>module load arch/<arch></code> sets the environment variable <code>ARCH=<arch></code>. This is done automatically on each node. If you want to override it, you must run </code>module load arch/<arch></code> explicitly.

			== Testing Modules on the Login Nodes and different Partitions ==

			You can always use <code>srun</code> or <code>salloc</code> to test your code (see [[NEMO2/Slurm#Interactive_Jobs\|Interactive Jobs]] and [[NEMO2/Slurm#Partitions\|Partitions]]).
			For quick tests for up to 15 minutes on the login nodes, you can use <code>srun -p login</code> or <code>salloc -p login</code>.
			If you get an MPI or memory error, try <code>srun [...] <program></code>.

	== Long Module Listings and Extensions ==		== Long Module Listings and Extensions ==

← Older revision		Revision as of 16:49, 24 November 2025
Line 7:		Line 7:
	== Resources ==		== Resources ==

	* '''Building your own modules:''' [[NEMO2/~~Easybuild_Modules~~/~~EB_Build_Module~~]] - Complete guide for the <code>eb-build-module.sh</code> script		* '''Building your own modules:''' [[NEMO2/Easybuild Modules/EB Build Module]] - Complete guide for the <code>eb-build-module.sh</code> script
	* '''Available modules:''' [https://www.nemo.uni-freiburg.de/easybuild-modules/ NEMO EasyBuild Modules List]		* '''Available modules:''' [https://www.nemo.uni-freiburg.de/easybuild-modules/ NEMO EasyBuild Modules List]
	* '''EasyBuild official website:''' https://easybuild.io/		* '''EasyBuild official website:''' https://easybuild.io/
Line 85:		Line 85:
	If you need software that is not yet available as a module on NEMO2, you can build your own EasyBuild modules. NEMO2 provides the <code>eb-build-module.sh</code> script that makes this process straightforward.		If you need software that is not yet available as a module on NEMO2, you can build your own EasyBuild modules. NEMO2 provides the <code>eb-build-module.sh</code> script that makes this process straightforward.

	'''For complete documentation, see:''' [[NEMO2/~~Easybuild_Modules~~/~~EB_Build_Module~~]]		'''For complete documentation, see:''' [[NEMO2/Easybuild Modules/EB Build Module]]

	=== Why Build Your Own Modules? ===		=== Why Build Your Own Modules? ===
Line 221:		Line 221:
	=== Need Help? ===		=== Need Help? ===

	* '''Full script documentation:''' [[NEMO2/~~Easybuild_Modules~~/~~EB_Build_Module~~]]		* '''Full script documentation:''' [[NEMO2/Easybuild Modules/EB Build Module]]
	* '''EasyBuild documentation:''' https://docs.easybuild.io/		* '''EasyBuild documentation:''' https://docs.easybuild.io/
	* '''Available easyconfigs:''' Use <code>eb-build-module.sh -s pattern</code> to search		* '''Available easyconfigs:''' Use <code>eb-build-module.sh -s pattern</code> to search