@@ -277,14 +277,14 @@ There are several partitions/queues in slurm intended for general usage:
...
@@ -277,14 +277,14 @@ There are several partitions/queues in slurm intended for general usage:
When a partition isn't explicitly specified with the “-p” parameter, the automatic routing mechanism determines the right partition for the job:
When a partition isn't explicitly specified with the “-p” parameter, the automatic routing mechanism determines the right partition for the job:
- "mpi" partition:
- "mpi" partition:
- when the memory specification is core oreiented (mem_per_cpu) and multiple tasks are specified
- when the memory specification is core oriented (mem_per_cpu) and multiple tasks are specified
- when multiple nodes are specified
- when multiple nodes are specified
- "bigsmp”: when the requested memory exceeds 750GB per node
- "bigsmp”: when the requested memory exceeds 750GB per node
- "smp": in all other cases
- "smp": in all other cases
In order to get access to GPU cards, make sure to specify the “gpu” partition as well as the type and number of GPU cards with the “-G” parameter, e.g. “-p gpu -G h100:2” in order to get 2x H100 GPU Cards. Types like “h100_2g. 24gb” are instances of the H100 card created by [MIG](https://docs.nvidia.com/datacenter/tesla/mig-user-guide/)(multi-instance GPU) partitioning, they behave like a separate device.
In order to get access to GPU cards, make sure to specify the “gpu” partition as well as the type and number of GPU cards with the “-G” parameter, e.g. “-p gpu -G h100:2” in order to get 2x H100 GPU Cards. Types like “h100_2g. 24gb” are instances of the H100 card created by [MIG](https://docs.nvidia.com/datacenter/tesla/mig-user-guide/)(multi-instance GPU) partitioning, they behave like a separate device.
Each user has a default group account in slurm which corresponds to his workgroup (not uniuser/hpcuser/smail). For each job the right group account must be specified with the “-A” parameter. Without it the default group account will be chosen automatically. The default group account can be found out by executing the following command:
Each user has a default group account in slurm which corresponds to his workgroup (not uniuser/hpcuser/smail). For each job the correct group account must be specified with the “-A” parameter. Without it, the default group account will be chosen automatically. The default group account can be found out by executing the following command:
```
```
sacctmgr show assoc -n user=$USER format=Account
sacctmgr show assoc -n user=$USER format=Account
...
@@ -292,7 +292,7 @@ sacctmgr show assoc -n user=$USER format=Account
...
@@ -292,7 +292,7 @@ sacctmgr show assoc -n user=$USER format=Account
## 6. `module` - selecting your software environment
## 6. `module` - selecting your software environment
`module` is a user interface to the Modules package, which provides for the dynamic modification of the user's environment via module‐files. This helps avoid software conflicts due to incompatibilities, versioning, dependencies, etc. Further, module-files allow for concurrent usage of different software versions, for example, when cross-checking executable-output of new compiler versions.
`module` is a user interface to the Modules package, which allows the dynamic modification of the user's environment via module‐files. This helps avoid software conflicts due to incompatibilities, versioning, dependencies, etc. Further, module-files allow for concurrent usage of different software versions, for example, when cross-checking executable-output of new compiler versions.
Your shell-initialization script can select frequently used modules. For example, an entry in your `~/.bashrc` file might look like this:
Your shell-initialization script can select frequently used modules. For example, an entry in your `~/.bashrc` file might look like this:
`module load lang/Julia/1.9.3-linux-x86_64 lang/Python/3.11.5-GCCcore-13.2.0 # load My Favorite Things`
`module load lang/Julia/1.9.3-linux-x86_64 lang/Python/3.11.5-GCCcore-13.2.0 # load My Favorite Things`