User Tools

Site Tools


start

Mogon I & II

News

News from our group and our “mogon ticker” with software / work related news can be found at our webpage. The easiest way to get informed about our news is to subscribe to our rss-feed.

Documentation

Policies

The regulations for use of the data center (ZDV) apply at all times. Further Policies are listed per item:

Mogon - Cluster Odds & Ends

Working on Mogon / Using our job scheduler

Usage

ATLAS specific usage

Performance Analysis Tools and Optimization Tools / Aspects

Monitoring systems

How to acknowledge Mogon

When preparing a journal publication please reference Mogon. We prepared a basic acknowledgement.

Training & Outreach

Courses

We offer various courses, particularly for newcomers via the university's Ilias e-learning system, where you can register for our courses. If you do not have a university account, please write to hpc@uni-mainz.de to register or ask for more information.

All courses, unless otherwise noted, will take place within the rooms of the ZDV. You will find us here.

HPC-Workshop

There is a regular meeting of HPC users and administrators for news, discussions and support.

We meet every thursday morning, at 10:15 am, in the 01 332 HPC-Workshop in the new building of the ZDV (Map - on the left side of the map).

If possible, please drop us a quick note beforehand and tell us what exactly you want to talk about (a specific problem or a general introdcution), so we can make sure that the appropriate person will be there.

How to get support

If you have any questions or need help regarding high performance computing at the ZDV, send an eMail to hpc@uni-mainz.de (which will create a new ticket in our ticketing system).

Please do not send eMail to our staff directly - using the ticketing system helps us with appropriate scheduling and load balancing while supporting you and every other user.

If you write an eMail, please try to include as much information as possible, including, but not limited to:

  • The job command line or the job script (sbatch …)
  • JobIDs
  • The environment you started the job in (at least the output of module list, maybe even env | sort)
  • If possible, the whole job output, or if it is to big, the relevant output from the batch system (at the beginning and the end) and any error messages you encounter.
start.txt · Last modified: 2017/11/22 08:50 by baumg001