Skip to content

Commit ba30696

Browse files
committed
added information for the cobra system
1 parent 0be3c28 commit ba30696

File tree

1 file changed

+49
-4
lines changed

1 file changed

+49
-4
lines changed

book/content/tools/02_hpc/03_parallel_fds.md

Lines changed: 49 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -52,7 +52,7 @@ jrlogin06.jureca
5252
````
5353

5454

55-
## FDS Module on JURECA
55+
### FDS Modules on JURECA
5656

5757
Modules offer a flexible environment to manage multiple versions of software. This system is also used on JURECA: [Module usage on JURECA](https://apps.fz-juelich.de/jsc/hps/jureca/software-modules.html).
5858

@@ -71,14 +71,37 @@ Thus, adding this line to your batch scripts and startup script (`~/.bashrc`) wi
7171
7272
````
7373

74+
## Accessing the CoBra / Pleiades Cluster
75+
76+
### Accounts
77+
78+
Please contact Lukas for an account.
79+
80+
### Login
81+
82+
Using the provided credentials, you can use SSH to login to the front-end `fugg1.pleiades.uni-wuppertal.de`.
83+
84+
85+
### FDS Modules on the CoBra Cluster
86+
87+
As on JURECA, the modules need to be added to the user's environment with
88+
89+
```module use -a /beegfs/larnold/modules```
90+
91+
The (default) FDS module can be loaded with
92+
93+
```module load FDS```
94+
95+
which sets up the environment to run FDS in parallel. The name of the FDS executable is `fds`.
96+
7497
## Job Submission
7598

76-
A computercluster is often used by a lot of users. Therefore executing a programm which needs a lot of the CPU power could disturb other users by slowing down the rest of the softwares or even the OS. The solution to this is a queueing system which organizes the execution of many programms and manages the ressource distribution among them. JURECA uses the software called Slurm for queueing and distributing to compute nodes. More information is provided in [JURECA's batch system documentation](https://apps.fz-juelich.de/jsc/hps/jureca/batchsystem.html).
99+
A computercluster is often used by a lot of users. Therefore executing a programm which needs a lot of the CPU power could disturb other users by slowing down the rest of the softwares or even the OS. The solution to this is a queueing system which organizes the execution of many programms and manages the ressource distribution among them. JURECA and the CoBra-cluster use the software called Slurm for queueing and distributing to compute nodes. More information is provided in [JURECA's batch system documentation](https://apps.fz-juelich.de/jsc/hps/jureca/batchsystem.html) and [Pleiades batch system](http://www.pleiades.uni-wuppertal.de/index.php?id=slurm).
77100

78101
Instead of running our simulation on the cluster we either submit our simulation file to the queueing system or execute a submit code which includes the modules we need for FDS, sets the number of processes, theads and other important quantities.
79102

80103

81-
### Single Job
104+
### Single Job on JURECA
82105

83106
The structure of a Slurm job script is basically a shell script. This shell script will be executed by the batch system on the requested resource. The definition of the resource is done as comments (`#`) with the `SLURM` keywords. These are instructions for Slurm.
84107

@@ -101,7 +124,7 @@ The individual lines have the following functions
101124

102125
```#SBATCH --account=ias-7```
103126

104-
On Jureca you need to have a computing time project and your account needs to be assinged to it. This budget is used to "buy" a normal/high priority in the queueing system. Using `account` you specify which computing time contingency will be debited for the specified job. Here `ias-7` is indicating the project we will use for this lecture. It is the budget of the IAS-7 at the Forschungszentrum Jülich.
127+
On JURECA you need to have a computing time project and your account needs to be assinged to it. This budget is used to "buy" a normal/high priority in the queueing system. Using `account` you specify which computing time contingency will be debited for the specified job. Here `ias-7` is indicating the project we will use for this lecture. It is the budget of the IAS-7 at the Forschungszentrum Jülich.
105128

106129
* **Partition**
107130

@@ -164,6 +187,28 @@ The current status of a user's queue can be listed with
164187
> squeue -u $USER
165188
```
166189

190+
### Single Job on the CoBra-Cluster
191+
192+
A simple script to execute FDS on a given input file is as follows:
193+
194+
```
195+
#!/bin/sh
196+
#SBATCH --job-name=fds_job_name
197+
#SBATCH --partition=normal
198+
#SBATCH --time=0-01:00:00 # days-hours:minutes:seconds
199+
#SBATCH --ntasks=24
200+
#SBATCH --nodes=1
201+
#SBATCH --output=stdout.%j
202+
#SBATCH --error=stderr.%j
203+
204+
module use -a /beegfs/larnold/modules/
205+
module load FDS
206+
207+
srun fds *.fds
208+
```
209+
210+
In contrast to JURECA, it is possible to run jobs for more than 24 hours.
211+
167212
### Chain Jobs
168213

169214
As there is a limit of 24 hours on JURECA, each job has to restart after this time. The following scripts automate the process for FDS on JURECA. It is important that the FDS input file has the `RESTART` parameter defined, typically initailly set to `.FALSE.`.

0 commit comments

Comments
 (0)