With sponsorship from hardware and software vendor partners, competing student teams design and build small clusters, learn scientific applications, and apply optimization techniques for their chosen architectures in a non-stop, 48-hour challenge.
Teams are comprised of six students and an advisor. Get your team together, apply, and show your compute chops to the HPC community.
Student Cluster Competition
Monday–Wednesday, 15–17 Nov 2027
Student Cluster Competition Chair Co-Chairs
Stephen Bird, University of Notre Dame
Abhinav Thota, Indiana University
Student Cluster Competition (SCC) Applications Open 1 March 2027
MON 1 MAR 2027
Applications Open
FRI 14 MAY 2027
Applications Close
FRI 18 JUN 2027
Notifications Sent
Teams are composed of six students, an advisor, and vendor partners. The advisor provides guidance and recommendations, the vendor provides the resources (hardware and software), and the students provide the skill and enthusiasm. Students work with their advisors to craft a proposal that describes the team, the suggested hardware, and their approach to the competition. The SCC committee reviews each proposal, ranks, and selects the team roster for the competition. The requirements for teams, the selection process, and what makes a good proposal are described more completely below.
SCC Connect is a virtual companion competition to the SCC that shares many of the same goals. SCC Connect teams compete using provided cloud resources and are not required to partner with a vendor, assemble a cluster, or attend the conference.
Each year, far more team applications are received than can possibly be brought to the conference. It takes a significant amount of time and effort to put a team together, so SCC Connect was formed to provide additional opportunities for these teams to apply their hard work, gain experience, and maintain momentum for future years.
Teams applying to the SCC may indicate they would like to be considered for SCC Connect if they are not selected to the SCC. Teams who do not indicate they are interested in SCC Connect will not be considered if not selected for the SCC. Indicating you would like to be considered for SCC Connect is not a guarantee to be selected for the competition.
Teams may also apply directly to SCC Connect without being considered for the SCC. This serves as a lower bar for entry for teams that may not have existing strong vendor relationships or sufficient funding to travel to the conference, or who are looking to gain a footing in the cluster competition world before applying to the SCC. The goal for teams participating in the SCC Connect is that they will be able to travel to the conference and compete in the SCC in a later year.
Final selections will be made considering the strength of the application, motivations as they relate to the goals of SCC Connect, and the team’s level of experience within prior cluster competitions.
Students, with the guidance of their advisor, will craft a proposal that describes their team, the proposed hardware and software, their approach to the competition, and what they hope to get out of the experience. This proposal is submitted as a team application for review by the SCC committee. The application consists of several prompts detailed below.
Your proposal will describe your team members, their strengths and weaknesses, and how everyone will work together in order to successfully compete. A good proposal will describe how the team members have different strengths and skills (i.e., academic studies and inclusion of non-STEM majors) and how they will work together and contribute to a strong team. This should not be a simple list of each team member’s qualifications–the reviewing committee will want to see how you will work together as a team.
Additionally, you will need to describe your team’s diversity. This does not mean academic diversity, but rather diversity in other areas such as underrepresented groups in your home region and institution. Diversity is relative to where you are from, so it can be helpful to describe what diversity means to your team and institution. You should also describe what efforts you made to recruit a diverse team – this is especially important if your team is not as diverse as you would have liked.
Your applications should describe in detail the hardware you propose to bring, and the software you plan to install (such as OS, resource managers, compilers, etc). A good proposal will provide sufficient detail to the reviewing committee that your proposed hardware and software meet the requirements outlined in the rules, and that you have thought through a plan on how to build and run your cluster. You should also explain how and why the hardware architecture you chose will be a great fit for typical real-world users and their workloads.
You will then need to describe the team’s relationship with your institution and vendor. Describe any financial support your institution and/or vendor is providing, such as travel expenses, cluster shipping, meals, etc. You should also describe any training or resources they are providing to help you prepare. It takes a village to build a team, so we want to see that you have a village backing you.
Next you will describe how your team will prepare for the competition. We are looking for evidence that you have a plan to prepare. This could include things like meeting regularly to work on the cluster, explore topics, practice, attend guest lectures, etc. Mentioning any classes the team members are taking that directly relate to the competition may also be helpful, but be sure to explain how they will benefit the team rather than listing a course catalog.
Finally, you will describe your team’s educational goals and what your team hopes to gain by participating in the competition. You should be as specific as possible with your goals rather than listing vague high level goals – we want to know what makes your team unique!
Selected teams receive full conference registration for each team member and one advisor. Each team is also provided with lodging for the students and advisor. As the competition is part of the Students@SC program, students can also participate in mentoring and networking events like the Mentor–Protégé Matching program as well as the full slate of student programming. Travel to the conference, shipping for your cluster, and per diem are not provided.
The SCC Committee will review the student clusters for operational readiness. Think of a typical real-world, user-facing supercomputer that computing centers run. How does your cluster compare to those clusters and how ready is it for hypothetical end users? The evaluation can include the following areas: user and admin accounts, adding new users, job scheduler/management, cluster networking, security, monitoring, software environment management, etc. A detailed grading rubric will be shared in the coming months.
Added in Spring/Summer 2027 timeframe.
Q: Can we recruit alternate team members? Do we include their names on the application? Can alternate team members attend SC and participate in Students@SC even if they do not participate in the cluster competition?
A: You are welcome to recruit alternates, however, only the 6 team members are considered part of the team. They do not receive any support from the conference through the SCC (like registration or hotel). It wouldn’t hurt to mention you have alternatives in your application text, but that is not required (and we don’t need all their details). They are certainly more than welcome at the conference and in the Students@SC program (it is open to all students), they will just need to secure arrangements through other means.
Q: How much can we modify software for the competition, such as the kernel, slurm/job runner, libraries, and benchmark code?
A: You can modify software as needed for the competition, including the kernel, slurm/job runner, libraries, and benchmark code. The only requirement is that the software must be publicly available (free or otherwise) and not subject to non-disclosure agreements. Any modifications must be shared with the committee, especially for application codes, at least 2 weeks before the competition. Teams are encouraged to share any improvements upstream to benefit the wider community.
Q: What is the judging process like for the finals?
A: The final scoring is a combination of various competition components, including benchmark scores, completion of challenges, judging interviews, and possibly posters and other activities. The final score is based on a holistic evaluation of the team’s performance across these areas.
Q: How important is the vendor relationship for being accepted? (SCC-only)
A: Having a vendor or institution committed to providing hardware is essential for your application. While the final hardware configuration may change over time, you should have a solid plan in place for what you intend to bring to the competition at this stage.
Note: In SCC Connect, the organizing committee provides the necessary cloud-based HPC hardware to all accepted teams. SCC Connect teams are welcome and encouraged to solicit vendors to support them with optional travel to the conference, provide meals during training, the competition, training, etc; however, this is not a consideration during team application review/selection for SCC Connect teams.
Q: How should I brand and represent my team if it includes students from multiple universities?
A: Consider geographical or national affiliations if your team comprises students from your region or country. The team’s name and branding can be adjusted as needed without affecting the team’s qualification or composition. If another team from your region/country joins the competition separately, it does not impact your team’s qualification or status in the competition. Each team’s identity and qualification are based on their actual composition of students, vendors, and support, regardless of geographical or national affiliations.
Q: Can we have cluster components sitting on the floor or on a palette?
A: No. Anything that is intended to be rackable needs to be in the rack. No cardboards/wooden palettes/bare floor.
Q: Our cluster consists of servers + desktop computers. Since we cannot put the desktop computer on the rack, we have to put it on the floor. Is this allowed?
A: As a desktop computer is intended to just sit on a surface, it is fine for it to sit on the floor. Please make sure it is not a trip hazard.
Create an account in the online submission system and complete the form. A sample form can be viewed before signing in.
If you have questions about SCC applications, please contact the program committee.
A cluster competition with the intent to create a more education-focused track of the Student Cluster Competition.