Complete cluster documentation, including detailed hardware specifications, can be found on the cluster documentation page.
The primary purpose of Turing is for performing computationally intensive simulations related to graduate and postdoctoral research. Undergraduate research assistants and certain MQP projects are also eligble to use Turing if their computational needs exceed what is available on Ace.
Turing is currently composed of 46 compute nodes with a variety of resources. The heterogeneous nature of Turing is intentional, and important to meet the diverse needs of the many comptutational science projects at WPI.
When users log into Turing, a summary of the most recenty configuration of Turing is printed. The login printout is always the most up-to-date configuration, and may be different from what is listed below.
The primary function of the Ace cluster is to provide a robust development environment for writing and debugging code, running test simulations, and intensive analysis/visualization of results from Turing.
Good examples of intended use of Ace include:
- Developing Python code using PyCharm
- Compiling code using gfortran/gcc/ifort/icc
- Debugging applications using gdb
- Writing and testing job submission scripts for use on Turing
- Running Tensorboard
- Testing code parallelization and single node scalability
There are also currently seven compute nodes available for up to two days of compute time. Compute nodes on both Ace and Turing are run using the Slurm batch manager. Extensive documentation of the policies in place for compute nodes are outlined elsewhere.
The compute nodes on Ace include a variety of resources meant to enable users to prepare for larger research simulations on Turing. This includes some nodes connected with Infiniband, as well as 14 NVIDIA K20s.