| marp | true |
|---|---|
| html | true |
| theme | default |
| paginate | true |
| header | Hopper Overview |
| footer | April 23, 2026 |
Rob Bjornson Director of Biomedical Research Support Yale Center for Research Computing
- YCRC
- Who was Hopper?
- Why do we need Hopper?
- Do I need to use Hopper?
- Hopper resources
- How is Hopper like other YCRC clusters?
- How does Hopper differ from other YCRC clusters?
- Resources
- Questions
- Independent center under the Provost's office
- Created to support your research computing needs
- Focus is on high performance computing and storage
- ~25 staff, including applications specialists and system engineers
- Available to consult with and educate users
- Ph.D. in Mathematics from Yale in 1934
- Pioneering computer scientist
- Trailblazer in creating first compiled computer languages
Many datasets now require a higher level of security than Bouchet provides.
- Data Use Agreements (DUAs)
- NIH controlled access datasets (e.g. dbGaP)
Hopper complies with:
- NIST 800-171 standard
- HIPAA standard
- Can meet other specific DUAs
- ~6000 cpus
- GPUs
- 40 a5000
- 40 l40s
- 40 a40
- 40 H200
- 60 H100
- 48 B200 coming
VAST 2.4 PiB
https://docs.ycrc.yale.edu/clusters/hopper/#partitions-and-hardware
In most ways, Hopper will be familiar to you:
- Slurm jobs
- Partitions: devel, day, week, gpu ...
- Open On Demand (but inside VDI)
- Software modules
- Home, work, scratch directories
- Getting access
- User Interface (VDI)
- Security measures and rules
- No internet access
- Data transfer
- Software installation
- Usage charges
- Projects, not Groups
- Storage allocations
We'll touch on each in turn
Access to the system is a multi-step process:
- PI submits a project https://research.computing.yale.edu/secure-project-request
- Health Science IT (HSIT) consults with PI and approves request
- PI completes required training http://research.computing.yale.edu/regulated-research-training
- YCRC creates new project, PI account, and associated linux group: netid_projname
- Other lab members can join https://research.computing.yale.edu/hopper-account-request
Of note: a PI can and should submit separate project requests for each individual project (e.g. IRB)
- Hopper's only user interface is a Virtual Desktop Infrastructure (VDI)
- You must be on the Yale VPN even when on campus
- Two ways to access VDI
- Via browser: https://hopper.ycrc.yale.edu
- Via dedicated ThinLinc client. https://www.cendio.com/thinlinc/download
- You will receive a (silent) DUO prompt each time
- The VDI is the equivalent of a login node
- VDI provides terminal, firefox, Open On Demand
- Session is persistent for extdnded period
- Each user has one unique VDI session
- The VDI prevents copy/pasting with the host computer, prevents file transfers and enforces idle session timeouts.
- Cut/Copy/Paste inside Hopper is allowed (right click + copy/paste)
- External screenshots, screen recording and screen sharing (e.g. via Zoom) are strictly prohibited.
- Internal screenshots can be made with ThinLinc client.
- If you know you will be away from your computer for more than 10 minutes, you must disconnect from the VDI by closing the browser tab or exiting the client.
- You must access Hopper from a private location, such as your home or office. Access from public locations such as coffee shops, transportation hubs or libraries is not allowed.
- Do not put sensitive data (e.g. patient information, personal identifiers) in directory names or job names, which might expose this information.
- Maintenance (usually less than 1 day) is done quarterly.
- From Hopper, you are not able to directly access anything outside of Hopper.
- All file transfers in and out are mediated by YCRC staff
- With some exceptions, all software installs mediated by YCRC staff
- Moving data into and out of Hopper requires submitting a request
- We distinquish between Low Risk and Sensitive Data
- Low Risk Transfer In or Out: https://research.computing.yale.edu/hopper-low-risk-transfer : scripts, deidentified data, data files with no PHI, PII, etc.
- Sensitive Data Transfer In: https://research.computing.yale.edu/hopper-sensitive-transfer : everything else
- Sensitive Data Transfer Out: contact YCRC
- Use globus to upload your data to your folder in the "Yale CRC Hopper Low Risk" collection.
- Submit https://research.computing.yale.edu/hopper-low-risk-transfer
- YCRC will move your data from the collection to your desired location on Hopper
- Download is the same in reverse
- Submit https://research.computing.yale.edu/hopper-sensitive-transfer first.
- YCRC will approve, make all necessary networking changes, and create a temporary globus receiving collection
- You will receive instructions on how to transfer your data.
Transfers requiring method other than globus are possible with YCRC assistance.
Transfer of sensitive data out is currently handled on a case-by-case basis. Please contact YCRC.
- Since you have no internet access, most software installation must be done by YCRC.
- The applications will generally be made available as modules.
There are two exceptions allowing self-service:
- python packages from the default anaconda repo. Note: NOT conda-forge
module load miniconda
conda create/install ...
- many approved R packages from CRAN. Use
install.packages()
For all other software, first search the modules, then contact YCRC.
You may transfer in scripts. You may transfer in and compile code written by you or others in your lab. This is considered a low risk transfer.
You may NOT transfer in and compile code written elsewhere. Ask us to download and build it for you.
Unlike YCRC's other clusters, currently all use of Hopper incurs compute charges.
Current Rates:
| type | cost/hour |
|---|---|
| CPUs | $0.004 |
| mid-range GPU | $0.49 |
| H200/B200 | $0.99-1.49 |
Storage beyond free quota: $5.15/TiB/month
See https://docs.ycrc.yale.edu/clusters/hopper/#rate-structure
Accounts on Hopper are different from other YCRC clusters
- Each logical Project is set up independently, with its own linux group and membership
- Projects are intended to be impermanent. Once the research project is complete, the project is terminated
- Projects must be reauthorized annually.
- PIs can and should have multiple Hopper projects if working on unrelated research projects
- Each project has its own work and scratch directories
- However, each user has a single home directory
| space | size | snapshots |
|---|---|---|
| home | 125 GiB | 7 days |
| work | 1 TiB | 7 days |
| scratch | 10 TiB | NO |
| PI | charged | NO |
Aside from the snapshots, no data is backed up!
- Hopper doc https://docs.ycrc.yale.edu/clusters/hopper
- Reach out to YCRC: email ycrc@yale.edu
- Hopper-specific Office Hours https://yale.zoom.us/my/ycrcsupport: Thurs 2-3pm
- Please do not send us screen shots!
- We cannot view your screen over zoom. Instead, we can join your VDI session
- What level of data differentiates Bouchet and Hopper?
- Can YNHH EPIC data be stored on Hopper? Yes
- How do I transfer data from NIH repositories such as ABCD to Hopper? Sensitive transfer
- Is this is the best cluster to use for analyzing sequencing data? No. McCleary is still the cluster to use
- Can Hopper be coordinated with the YNHH data brokers (JDAT) so we can take clinical identifiable data from the hospital to Hopper? Yes
- Please explain when Milgram is still appropriate. Milgram is reaching EOL. New usage will be on Hopper or Bouchet
- Can people with sponsored identities use Hopper? Not currently
Please help us improve this workshop by sharing feedback via a 2-minute anonymous survey. Thank you.
https://yalesurvey.ca1.qualtrics.com/jfe/form/SV_dgL2LLO0KpHWYqq
Scan the QR Code:



