High Performance Computing

For using our compute cluster you need a GWDG account. This account is, by default, not activated for the use of the compute resources. To get it activated, please send an informal email to hpc@gwdg.de

Once you gain access, you can login to the frontend nodes gwdu101.gwdg.de, gwdu102.gwdg.de and gwdu103.gwdg.de. These nodes are accessible via ssh from the GÖNET. If you come from the internet, first login to login.gwdg.de. From there you can then reach the frontends. The frontends are meant for editing, compiling, and interacting with the batch system, but please don't use them for testing for more than a few minutes, since all users share resources on the frontends and will be impaired in their daily work, if you overuse them. gwdu101 is an AMD based system, while gwdu102 and gwdu103 are Intel based. If your software takes advantage of special CPU dependent features, it is recommended to use the same CPU architecture for compiling as targeted for running your jobs.

The following documentation is valid for this list of hardware:

Explanation: Systems marked with an asterisk (*) are only available for research group participating in the corresponding hosting agreement. GB = Gigabyte, TB = Terabyte, Gb/s = Gigabit per second, GHz = Gigahertz, GT/s = Giga transfer per second, IB = Infiniband, QDR = Quad data rate, FDR = Fourteen Data Rate.

For a complete overview of hardware, located in Göttingen, look at http://hpc.gwdg.de/systems.html

Most of the third-party software installed on the cluster is not located in the default path. To use it, the corresponding “module” must be loaded. Furthermore, through the module system you can setup environment settings for your compiler to use special libraries. The big advantage of this system is the (relative) simplicity with which one can coordinate environment settings, such as PATH, MANPATH, LD_LIBRARY_PATH and other relevant variables, dependent on the requirements of the use-case. You can find a list of installed modules, sorted by categories, by entering module avail on one of the frontends gwdu101 or gwdu102. The command module list gives you a list of currently loaded modules.

To use a module, you can explicitly load the version you want with module load software/version. If you leave out the version, the default version will be used. Logging off and back in will unload all modules, as well as module purge. You can unload single modules by entering module unload software.

The recommended compiler module for C, C++, and Fortran code is the default Intel compiler intel/compiler. We also provide GNU and Open64 compilers, the PGI compiler suite will follow. Open64 is often recommended for AMD CPUs, but we do not have experience with it. For math (BLAS and fftw3) the Intel MKL is a good default choice intel/mkl, with ACML being an alternative for AMD processors. Usually it is not necessary to use fftw3 modules alongside with the MKL, as the latter provides fftw support as well. Please note that the module python/scipy/mkl/0.12.0 provides Python's numpy and scipy libraries compiled with Intel MKL math integration, thus offering good math function performance in a scripting language.

intel/mpi and the various OpenMPI flavors are recommended for MPI, mostly due to the fact that the mvapich and mvapich2 libraries lack testing.

• Running Jobs Slurm

old:

• Running Jobs
• Running Jobs (for experienced users)

Old (now part of Running Jobs Slurm):

You can find all important information about the newest nodes here

• Gaussian09
• IPython Parallel
• Jupyter
• Molpro
• Orca
• PSI4
• Turbomole
• Singularity

https://info.gwdg.de/wiki/doku.php?id=wiki:hpc:start

• Transfer Data

.bashrc

Courses

Using the GWDG Scientific Compute Cluster - An Introduction

script.sh.gz

Scientific Computing