Summary of Systems

Note that we have two generally-available “clusters,” faculty and ilab. The sections below will describe each. Each cluster has its own home directories. So if you have access to both ilab and faculty, you won’t be able to see your ilab home directory from the faculty systems and visa versa. There is a common file system shared by all clusters, /common/users. Your directory on it is /common/users/NETID. Quotas on /common/users are 100 GB.

IMPORTANT CS Linux System has enforced limitations that all users should be aware of. Make sure to check the page before running a big job.

Systems Status

Current System Status


Faculty offices, plus some servers. There are two serversconstance.cs and porthos.cs. However we recommend logging in to That will give you either constance.cs or porthos.cs, randomly. If one is down it will give you the one that is up.

These are not very powerful systems. They’re intended primarily to keep records in an environment with no students. Serious computing is normally done on the research cluster.

Faculty Machines


A set of three large servers (including 1080Ti GPUs and an instructional Hadoop cluster), and the Ilab (2nd floor Hill Center) and grad student offices. Most students access these systems remotely, by ssh, X2Go or XRDP.  Please use the alias,which will give you one of the three large servers. You can also look at the iLab status page to find a desktop system that isn’t in heavy use.

More informaton about Student systems, and instructions on using them

Instructional Laboratory (iLab) Systems: Announcements and information about rooms

Research cluster

Servers for use by faculty and grad students working on research projects. Faculty can authorize students to have access. The major system here is aurora, a large multi-core system with SSD storage. 

Research Machines

Research Web Server


Many of our systems have GPUs:

  • 30 of the Ilab systems have Nvidia GT 730 or Radeon R9-360
  • The 3 ilab servers each have 8 1080Ti GPUs
  • atlas.cs: K40, QuadroK4000
  • cray1.cs: 2 K80
  • gpu.cs: K40, Titan

CBIM systems

CBIM has a set of servers with large memory and GPUs. Those outside CBIM need permission from Dimitri Metaxas to use them, but that is generally available for CS researchers.

  • 12 Dell systems with 4 K80 each, 512 G memory, 2 SSD
  • 3 HP systems, with 2 K80, 256 G memory, 13 TB disk

High-performance systems: OARC

OARC is a University group that provides high-performance computing. Computer science in general doesn’t have a conventional HPC cluster. We concentrate on GPUs and more specialized hardware. For large-scale HPC, OARC is the best source. They have a large cluster, Amarel. It is intended as a “condo” cluster. I.e. grants buy nodes, and are guaranteed at least as much capacity as they purchased. The cost is matched by the University. Howver some capacity is available for those who haven’t bought into the system, particularly for course work and student use.

For more information see the OARC web site.

Some of OARCs nodes have GPUs, typically Nvidia.

Virtual machines

LCSR can provide virtual machines, both for researchers and for use by classes. To request a system, please send mail to

Researchers commonly use VMs for web servers and other support services. We normally put those VMs on the same servers used for LCSR infrastructure.

For course use, we talk with the instructor to find out the configuration and software needed, then create one VM per user. We can also create VMs for grad students. These VMs are placed on one of two large (1 TB each) VM servers purchased specifically for instruction.

Virtual Machines for Student Academic Use

Virtual Machines for Faculty and Research


Windows Remote Desktop — NOTE: This service is discontinued FALL 2018 due to no usage

Getting Help

1. If you have issues with any CS computing resources

2. If you have issues with Non CS computing resources