Running Calculations

On your desktop computer, you start your calculations and they start immediately, run until they are finished, then your desktop does mostly nothing, until you start another calculation. A compute cluster has several hundred, maybe a thousand computers (compute nodes), all of them are busy most of the time and many people want to run a great number of calculations. So running your job has to include some extra steps:

1. prepare a script (usually a shell script), with all the commands that are necessary to run your calculation from start to finish. In addition to the commands necessary to run the calculation, this batch script has a header section, in which you specify details like required compute cores, estimated runtime, memory requirements, disk space needed, etc.
2. Submit the script into a queue, where your job (calculation)
3. Job is queued and waits in row with other compute jobs until the resources you requested in the header become available.
4. Execution: Once your job reaches the front of the queue, your script is executed on a compute node. Your calculation runs on that node until it is finished or reaches the specified time limit.
5. Save results: At the end of your script, include commands to save the calculation results back to your home directory.

There are two types of batch systems currently used on bwHPC clusters, called "Moab" (legacy installs) and "Slurm".

Because of differences in configuration (partly due to different available hardware), each cluster has their own batch system documention:

• Slurm systems
  • Slurm bwUniCluster 2.0
  • Slurm JUSTUS 2
  • Slurm Helix
• Moab systems (legacy systems with deprecated queuing system)
  • Moab NEMO specific information
  • Moab BinAC specific information

When you are running your calculations, you will have to decide on how many compute-cores your calculation will be simultaniously calculated. For this, your computational problem will have to be divided into pieces, which always causes some overhead.

How to find a reasonable number of how many compute cores to use for your calculation is described in the page

• Scaling

Please also see our advice for

• Energy Efficient Cluster Usage