Latest news for the Degond compute cluster

Welcome to the Degond HPC cluster

Re-launched in August 2021, this new cluster is a scaled-down version of the main Maths NextGen cluster; with a combined submission/compute node/cluster management server (kato) and 2 additional compute nodes, it is specifically tailored for the Degond section's use.

kato is the entry point to this cluster and assuming you already have access to this system, access is via ssh using your College computer account username and password as before. The former stand-alone compute servers lax and nash have now been integrated into the cluster as compute nodes, along with eight additional nodes stats01 to stats08 inclusive. Full documentation on this new facility can be found here.

Can I still access legacy data stored on kato, lax & nash?

Yes - user data currently stored on local disks in kato, lax and nash is still available on these disks. You can access kato exactly as you did before it was converted to a HPC node and, at present, you can access lax or nash from kato by first logging into kato and from there, into lax or nash as appropriate:

ssh kato

and then:

ssh lax


ssh nash

where you will find your local lax and nash files as before.

However, we are moving away from storing user data on local disks on the smaller compute systems in favour of making more use of networked storage so the data currently on the legacy kato, lax and nash servers will eventually move to a dedicated storage server that will be added to the Degond HPC cluster in due course. After this has been done, there will be no user data stored on these systems although you will still be able to access nash and lax via kato as described above.

Instead of logging into nash or lax from kato, you could also use the -I option to qsub to start an interactive Torque job, presenting you after a few seconds delay with a shell on the next available compute node as shown in this example:

andy@kato:~$ qsub -I
qsub: waiting for job to start
qsub: job ready

and typing 'exit' will end this session:
qsub: job completed

However, you can't choose the node you want to connect to in this way; Torque will connect you to the next least-heavily loaded node which may not be of much use if you want to access files on a particular node.

Any questions?

As always, I'll be happy to answer any questions you may have.

Andy Thomas

Research Computing Manager,
Department of Mathematics

last updated: 7.1.2022