The Savio cluster is open to all UC Berkeley PI’s who need access to high performance computing. Multi-institutional research collaborations involving at least one UC Berkeley PI are also welcome. Instructors of record can get access to Savio for their course through an Instructional Computing Allowance.
Obtaining Access to Savio
There are three primary ways to obtain access to Savio:
- For projects: requesting a block of no-cost computing time via a Faculty Computing Allowance (FCA). This option is currently offered to UC Berkeley faculty, who can then share their Allowance amongst their postdocs, grad students, staff researchers, and other campus research affiliates. See below for more on eligibility. For details, please see Faculty Computing Allowance. To request an FCA, please fill out the Savio access request form.
- For projects: purchasing and contributing Condo nodes to the cluster. This option is open to any campus PI, and provides ongoing, priority access to you and your research affiliates who are members of the Condo. For details, please see Condo Cluster Service.
- For courses: requesting an Instructional Computing Allowance (ICA), which provides a block of no-cost computing time for an instructor and students in a course. For details, please see Instructional Computing Allowance. To request an ICA, please fill out the ICA request form.
Faculty Computing Allowances are intended for faculty (PIs) who conduct research as a key part of their position. FCAs are available for:
- Assistant, associate, and full professors
- Emeriti (retired) assistant, associate, and full professors, who still have active PI status
- Adjunct professors
- Researchers in the Professional Research Series (with proof of job classification)
Lecturers are eligible for an FCA with a note from their department chair or dean stating that access is necessary for the lecturer’s work.
Instructional Computing Allowances are intended for any instructor of record of an official UC Berkeley course. In order to receive an ICA, an instructor must have a designated point of contact (typically the instructor or a teaching assistant) who handles software installation and all student troubleshooting and support. The designated point of contact can escalate issues to BRC staff, and work with BRC staff on software installation and account provisioning.
If you'd like to further discuss any of these options in more detail, or if you have any other questions, you're invited to contact us at firstname.lastname@example.org.
This training video also provides an overview of your options for accessing Savio:
Getting Additional User Accounts
After a new project (FCA or Condo) has been established, UCB researchers who want to request new user accounts on the cluster, to be associated with an existing project or projects, can submit the Additional User Account Request/Modification Form. PIs can also use the Request Form to submit account requests for non-UCB users associated with their project. Users wishing to get access to an additional project (FCA or condo) in addition to their current project(s) should also fill out the form.
All user account requests require the approval of the PI for the relevant project on the cluster.
Note: each new user will also need to complete a User Access Agreement Form. (For convenience, this access agreement form is linked from the user account request form, above.)
Accessing User Accounts
Please see the Logging In page for details regarding access to BRC user accounts. For security reasons, all access is via One-Time Passwords (OTPs), to reduce the risk of a compromise from stolen user credentials.
Closing User Accounts
The PI for the project is ultimately responsible for notifying Berkeley Research Computing when user accounts should be closed, and to specify the disposition of a user's software, files, and data.
For ICAs, all student accounts are closed and files are deleted at the end of the semester when the ICA expires, unless the student accounts are also associated with an FCA or condo.
For FCAs and condos, users’ accounts are not automatically deactivated upon termination of an employee because many people change their employment status, but remain engaged with a research project.
As well, in some cases users share software and data from their home directory, and others may depend on these. For these reasons, account terminations have to be requested by the PI, or the user of the account.