If you have never used a Cluster, or are not familiar with this cluster, YOU WILL WANT to read and follow the examples in the document to become familiar with how to run jobs on HPC. It is a common practice for new users to ignore this manual and simply try to run jobs without understanding what they are doing. Such carelessness can and WILL easily impact hundreds/thousands of critical jobs and users currently running on the cluster.
If your actions compromise the health of the HPC cluster, your account will be LOCKED so please make sure you run through the examples below before you embark on running jobs. Some important remarks to avoid this:
Using a High Performance Computing Cluster such as the HPC Cluster requires at a minimum some basic understanding of the Linux Operating System. It is outside the scope of this manual to explain Linux commands and/or how parallel programs such as MPI work. This manual (replace this with this page) simply explains how to run jobs on the HPC cluster.
When you login to HPC you are connected to what is called a login node. The HPC Cluster has several major components:
● Login nodes: The login nodes are meant for simple tasks such as submitting jobs, checking on job status, editing (emacs, vi), and performing simple tasks.
● A Head node: The head node runs all of the cluster critical services.
● Compute nodes: The compute nodes are the workhorse of the cluster. For
computational work both Serial or Parallel, in Batch mode or Interactive
mode, you will be using the compute nodes.
(Add how to use them in these different modes.)
If your problem is in any topic listed above, then It is very important that you read the document and watch the video.
Alternatively you can sent an email to email@example.com this will create a support ticket automatically.
When reporting problems, please give as much information as you can to help us in diagnosis, for example:
● Your username
● Queue/partition name
● Job ID(s)
● A copy of any error messages
● Command used to submit the job(s)
● Path(s) to scripts called by the submission command
● Path(s) to output files from your jobs
● When the problem occurred
● What commands or programs you were trying to execute at the time
● A pointer to the program you were trying to run or compile