You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/Documentation/Systems/Gila/modules.md
+71Lines changed: 71 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,6 +14,15 @@ When you log in to Gila, three modules are loaded automatically by default:
14
14
!!! note
15
15
The `DefApps` module is a convenience module that ensures both `Core` and `GCC` are loaded upon login or when you use `module restore`. It does not load additional software itself but guarantees that the essential environment is active.
16
16
17
+
## X86 VS ARM
18
+
19
+
There are two module stacks on Gila, one for each hardware architecture and each stack is loaded depending on the hardware used.
20
+
The two hardware stacks are almost identical in terms of modules offered, however some modules might be missing and/or have different versions. Please email [HPC-Help](mailto:HPC-Help@nrel.gov) for any request regarding modules availability and/or versions change.
21
+
The recommended usage is to connect to the login node corresponding to the hardware intended to be used for the compute, e.g. `gila-login-1` for **x86** and `gila-hopper-login1` for **arm**.
22
+
23
+
!!! warning
24
+
Usage of the GraceHopper computes from the x86 login node, or the usage of x86 computes from the GraceHopper login is not allowed and will cause module problems.
25
+
17
26
18
27
## Module Structure on Gila
19
28
@@ -71,6 +80,54 @@ Loading an MPI implementation makes MPI-enabled software that was installed with
71
80
72
81
This behavior ensures that only software built against the selected MPI implementation is exposed, helping users avoid mixing incompatible MPI libraries.
73
82
83
+
For example, using **module spider** to find all available variances of **HDF5**.
84
+
85
+
```bash
86
+
[USER@gila-login-1 ~]$ ml spider hdf5
87
+
hdf5:
88
+
--------------------------------------------
89
+
Versions:
90
+
hdf5/1.14.5
91
+
hdf5/1.14.5-mpi
92
+
```
93
+
94
+
Each version of **HDF5** requires dependency modules to be loaded so that they can be available to be used.
95
+
Please refer to the **module spider** section for more details.
96
+
97
+
To find the dependencies needed for **hdf5/1.14.5-mpi**
98
+
99
+
```bash
100
+
[USER@gila-login-1 ~]$ ml spider hdf5/1.14.5-mpi
101
+
102
+
hdf5:
103
+
--------------------------------------------
104
+
You will need to load all module(s) on one of the lines below before the 'hdf5/1.14.5-mpi' module is available to load.
To determine whether a software package is available on the cluster, use `module spider`. This command lists **all available versions and configurations** of a given software, including those that are not currently visible with `module avail`.
76
133
@@ -84,6 +141,20 @@ Container tools such as **Apptainer** and **Podman** do not require module files
84
141
This means you can use Apptainer and Podman at any time without loading a specific module, regardless of which compiler, MPI, or CUDA toolchain is currently active.
85
142
86
143
144
+
## Building on Gila
145
+
146
+
Building on Gila should be done on compute nodes and **NOT** login nodes.
147
+
Some important build tools are not available by default and requires loading them from the module stack.
0 commit comments