In 2011, the Research Computing Center (RCC) launched the high-performance compute cluster, Midway1, to enable research and scholarship. After 7 years, the hardware is no longer under warranty and is beyond its expected lifespan. The RCC has started the decommissioning of Midway1 and plans to migrate all applications to Midway2. A multi-phased approach is being used to decommission Midway1 as to mitigate disruption.

The first phase is the migration of the more than 600 software modules from Midway 1 to Midway2. We expect this to be completed by December 31, 2018. The second phase will be the decommissioning of Midway1 compute nodes. Phase two will be initiated in the first quarter of 2019 and is anticipated to be complete by April 1, 2019. The final phase will be the migration of data. Data migration will take time, and it has a target completion date of May 31, 2019. The RCC will offer data migration assistance, training, and support during this process. After this, we will move towards a full decommissioning. We expect this to take place by the end of June 2019.

Information about this project can be found at the in the FAQ section of this website. If you have questions about the decommissioning or would like assistance, contact us at (773) 795-2667,, or visit the walk-in lab at Regenstein Library room 216.


Frequently Asked Questions

Midway will be decommissioned in phases. We expect the final phase to be completed in June 2019.
You can find out what modules work on Midway2 here. If you still need help, you can send a request to
Partitions associated with Midway1 will no longer be available to run your jobs. Those partitions are: amd, sandyb, ivyb, gpu, bigmem, and mic. (A partition is a collection of compute nodes that all have the same, or similar, architecture and configuration.) For an overview of the midway1 and midway2 partitions, please visit this link.
Midway1 compute nodes are out of warranty and beyond their expected lifespan.
Users should test their programs on Midway2 to make sure they run with newer versions of hardware and software. Users will also need to update their scripts and replace references to the Midway1 partitions with Midway2 counterparts.
If you have never used Midway1, you will not be affected by this decommissioning.
Yes, it is most likely that you will. To make sure you take advantage of Midway2’s newer hardware and software it is highly recommended that you recompile your code on Midway2 before running them. If you have trouble compiling or running your code, please contact us at
Midway2 is accessible via its login nodes which can be reached at The same username and password you use for Midway1 will work on Midway2. See here for instructions.
You can find the data transfer user guide here.

Contact Us

If you need assistance regarding the decommissioning of Midway1, the RCC is here to support you.

Call the RCC Help Desk

(773) 795-2667

Email the RCC for Help

Visit the RCC Walk-in Lab

Walk-In Laboratory: Regenstein Library, Suite 216