The first block (with the `SBATCH` keyword) informs the system of the HPC resources we want to use. It requires an account name to which the compute time will be billed against, a maximum job time, how many tasks we want per node, how many nodes we want and how many CPUs we wish to use per task. Finally, since the HPC system is divided into **partitions** of nodes, we must specify which one we will use.
The first block (with the `SBATCH` keyword) informs the system of the HPC resources we want to use. It requires an account name to which the compute time will be billed against, a maximum job time, how many tasks we want per node, how many nodes we want and how many CPUs we wish to use per task. Finally, since the HPC system is divided into **partitions** of nodes, we must specify which one we will use.
For the problem we will run here, we will use:
For the problem we will run here, we will use:
- the account we will use is `training2226`
- the `dc-cpu-devel` partition
- the `dc-cpu-devel` partition
- use all of the CPUs in a single node (e.g., 64 in JURECA-DC)
- use all of the CPUs in a single node (e.g., 64 in JURECA-DC)
- only use one task, as all of our computational domain will be in the same node.
- only use one task, as all of our computational domain will be in the same node.
