skip to content

The Pat cluster is a set of workstations linked by a private gigabit ethernet network.

To access it, ssh to the head node which is . Use your Admitto credentials.

Homespace is on a mirrored pair of disks attached to the head node. The /home filesystem is 150GB in size and has quotas (currently 15GB soft, 20GB hard limit). It is backed up regularly. If you need access to backups please contact the helpdesk.

/home is shared to all nodes that are part of the cluster, so your job sees the same home directory wherever it is on the machine. It's important to remember that from a compute job's point of view accessing this directory is extremely slow, especially if all the nodes are trying at once. Compute jobs should always write data to a local disk if possible, and copy it back to /home at the end.

There is also a shared scratch filesystem /sharedscratch in which you will have a directory. These are not backed up. They have a quota restriction of 250Gb soft limit and 300Gb hard limit, but it is expected that most people will stay well within that amount. They have the same speed issue as /home.

Each node also has a local /scratch filesystem on which the queueing system will create you a directory when you use the node. These filesystems are about 1.8Tb in size (8TB on the cpu-only nodes) with no quota restriction and are the most appropriate place for your jobs to write temporary files during a run. They are local to each node and so considerably faster than the NFS-mounted /home and /sharedscratch. Please clean up files on /scratch when you are done with them.

A variety of compilers and libraries are installed. Like most local Linux machines the cluster has the modules environment to allow you to switch between different compilers and libraries. By default, no modules are loaded.

All compute jobs should be run through the queueing system. The queueing system will run each job on a free CPU and/or GPU, copying the output back to a user-specified file at the end of the job. The queueing system is SLURM. Please read the Pat SLURM documentation for more details.

System status 

System monitoring page

Can't find what you're looking for?

Then you might find our A-Z site index useful. Or, you can search the site using the box at the top of the page, or by clicking here.