<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Current Revision (25.04) :: Documentation for HPC</title><link>https://docs.hpc.gwdg.de/software_stacks/current/index.html</link><description>The default stack on the whole Unified HPC system in Göttingen. This stack uses Lmod as its module system. For the purposes of setting the desired software stack (see Software Stacks), its short name is gwdg-lmod. You can learn more about how to use the module system at Module Basics.
To see the available software, run
module avail The modules for this stack are built for several combinations of CPU architecture and connection fabric to support the various kinds of nodes in the cluster. The right module for the node is automatically selected during module load.</description><generator>Hugo</generator><language>en</language><atom:link href="https://docs.hpc.gwdg.de/software_stacks/current/index.xml" rel="self" type="application/rss+xml"/><item><title>Emmy Core Modules</title><link>https://docs.hpc.gwdg.de/software_stacks/current/emmy-p2-core/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.hpc.gwdg.de/software_stacks/current/emmy-p2-core/index.html</guid><description>These modules are loadable by default. No other modules have to be loaded first.
Tip The software packages loaded on each phase are optimized for the particular CPU and GPU architecture (machine kind) of that phase (e.g Intel Cascadelake or Intel Sapphirerapids).
You can print the current machine kind by using the command: /sw/rev_profile/25.04/machine-kind
If you compile your own code (e.g. by using gcc or pip) please take care to compile on the same machine kind that the code will also be executed on.</description></item><item><title>Emmy GCC11 Modules</title><link>https://docs.hpc.gwdg.de/software_stacks/current/emmy-p2-gcc11/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.hpc.gwdg.de/software_stacks/current/emmy-p2-gcc11/index.html</guid><description>It is required to load the appropriate compiler and MPI modules before any of the modules become visible (hierarchical module system):
module load gcc/11.5.0 module load openmpi/4.1.7 Tip The software packages loaded on each phase are optimized for the particular CPU and GPU architecture (machine kind) of that phase (e.g Intel Cascadelake or Intel Sapphirerapids).
You can print the current machine kind by using the command: /sw/rev_profile/25.04/machine-kind</description></item><item><title>Emmy GCC14 Modules</title><link>https://docs.hpc.gwdg.de/software_stacks/current/emmy-p2-gcc14/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.hpc.gwdg.de/software_stacks/current/emmy-p2-gcc14/index.html</guid><description>It is required to load the appropriate compiler and MPI modules before any of the modules become visible (hierarchical module system):
module load gcc/14.2.0 module load openmpi/4.1.7 Tip The software packages loaded on each phase are optimized for the particular CPU and GPU architecture (machine kind) of that phase (e.g Intel Cascadelake or Intel Sapphirerapids).
You can print the current machine kind by using the command: /sw/rev_profile/25.04/machine-kind</description></item><item><title>Emmy Intel Modules</title><link>https://docs.hpc.gwdg.de/software_stacks/current/emmy-p2-intel-impi/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.hpc.gwdg.de/software_stacks/current/emmy-p2-intel-impi/index.html</guid><description>It is required to load the appropriate compiler and MPI modules before any of the modules become visible (hierarchical module system):
Intel Compiler MPI Options Intel MPI Open MPI module load intel-oneapi-compilers/2025.0.0 module load intel-oneapi-mpi/2021.14.0 module load intel-oneapi-compilers/2025.0.0 module load openmpi/4.1.7 Tip The software packages loaded on each phase are optimized for the particular CPU and GPU architecture (machine kind) of that phase (e.g Intel Cascadelake or Intel Sapphirerapids).</description></item><item><title>Grete Core Modules</title><link>https://docs.hpc.gwdg.de/software_stacks/current/grete-p2-core/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.hpc.gwdg.de/software_stacks/current/grete-p2-core/index.html</guid><description>These modules are loadable by default. No other modules have to be loaded first.
Tip The software packages loaded on each phase are optimized for the particular CPU and GPU architecture (machine kind) of that phase (e.g AMD Rome + A100 or Intel Sapphirerapids + H100).
You can print the current machine kind by using the command: /sw/rev_profile/25.04/machine-kind
If you compile your own code (e.g. by using gcc or pip) please take care to compile on the same machine kind that the code will also be executed on.</description></item><item><title>Grete GCC13 Modules</title><link>https://docs.hpc.gwdg.de/software_stacks/current/grete-p2-gcc13/index.html</link><pubDate>Mon, 01 Jan 0001 00:00:00 +0000</pubDate><guid>https://docs.hpc.gwdg.de/software_stacks/current/grete-p2-gcc13/index.html</guid><description>It is required to load the appropriate compiler and MPI modules before any of the modules become visible (hierarchical module system):
module load gcc/13.2.0 module load openmpi/5.0.7 Tip The software packages loaded on each phase are optimized for the particular CPU and GPU architecture (machine kind) of that phase (e.g AMD Rome + A100 or Intel Sapphirerapids + H100).
You can print the current machine kind by using the command: /sw/rev_profile/25.04/machine-kind</description></item></channel></rss>