CryoSPARC-Sapelo2
Category
Engineering
Program On
Sapelo2
Version
4.3.1
Author / Distributor
See https://guide.cryosparc.com/
Description
"CryoSPARC (Cryo-EM Single Particle Ab-Initio Reconstruction and Classification) is a state of the art HPC software solution for complete processing of single-particle cryo-electron microscopy (cryo-EM) data. CryoSPARC is useful for solving cryo-EM structures of membrane proteins, viruses, complexes, flexible molecules, small particles, phase plate data and negative stain data." For more information, please see https://guide.cryosparc.com/.
NOTE: Users are required to be added into GACRC cryosparc group before they can run this software from Sapelo2. Please fill out the GACRC General Support form to request. We will reach out to you after we received your request.
Configurations
Master node VM:
- Host name: cryosparc.gacrc.uga.edu
- Intel Xeon processors (16 cores) and 64GB of RAM
- mongodb is installed and run on the master node
Worker nodes:
- One NVIDIA Tesla A100 node: Intel Xeon processors (64 cores), 1TB host RAM memory, 4 NVIDIA Tesla A100 GPU cards (80GiB device memory per card), and NVMe SSD 3570GB local drive.
- cryoSPARC recommends using SSD for caching particle data. /lscratch/gacrc-cryo is set up on the worker node for this purpose.
- The amount of space that cryoSPARC can use in /lscratch/gacrc-cryo is capped at 100GB.
cryoSPARC group: cryosparc
cryoSPARC service account: gacrc-cryo
- gacrc-cryo is the service account that will run cryoSPARC workflow jobs for all cryoSPARC users.
- Some tasks can only be handled by gacrc-cryo, like make a new lane of worker node(s), user management, and connect or update worker node(s) to master, etc..
- Regular CryoSPARC users can run cryosparcm on the master node to check cryoSPARC status, using cryosparcm status or cryosparcm checkdb.
cryoSPARC project space: /scratch/gacrc-cryo
User Login
There are two ways to access the CryoSPARC web interface. The recommended method is to connect through the UGA VPN and access the CryoSPARC web server directly. SSH tunneling remains available as an alternative if needed.
Method 1 (Recommended): VPN + Direct Web Access
- Connect to the UGA VPN using the Cisco Secure Client (Cisco AnyConnect) and select remote.uga.edu.
- Note: Even if you are working on campus, you must still connect to the UGA VPN before accessing the CryoSPARC web server.
- Open the URL for your assigned CryoSPARC instance in your web browser. For example:
- Log in using your registered UGA email address and CryoSPARC password.
- Note: Your registered UGA email address may be an email alias rather than your official MyID@uga.edu address. Please use the email address that was registered with your CryoSPARC account.
Method 2: SSH Tunnel
Users may also access CryoSPARC by establishing an SSH tunnel to expose port 39000 from the CryoSPARC master node to their local computer.
If you are using Linux or macOS, run the following command in a terminal:
ssh -N -L 39000:10.2.0.60:39000 username@cryosparc.gacrc.uga.edu
If you are using Windows, download plink program and run:
plink -ssh -N -L 39000:10.2.0.60:39000 username@cryosparc.gacrc.uga.edu
Place plink.exe in your current working directory, or specify its full path when running the command.
Unless you have configured SSH public key authentication, you will be prompted for your UGA MyID password and Duo authentication. After authentication succeeds, the SSH session will remain open. This is expected and indicates that the tunnel has been established successfully.
With the SSH tunnel active, open your web browser and navigate to:
http://localhost:39000
The CryoSPARC login page should appear.
Troubleshooting
If you are unable to access the CryoSPARC web interface:
- Verify that you are connected to the UGA VPN if you are using the recommended VPN + Direct Web Access method.
- Confirm that you are using the correct URL for your assigned CryoSPARC instance.
- Make sure you are logging in with your registered UGA email address and CryoSPARC password. Your registered UGA email address may be an email alias rather than your official MyID@uga.edu address.
- If you are using the SSH tunnel method, ensure that the SSH session remains active while accessing the web interface.
- If you have forgotten your CryoSPARC password, contact GACRC Support to request a password reset token.
- If the problem persists, please contact GACRC Support and include:
- The URL you are using to access CryoSPARC.
- Your UGA MyID and your registered UGA email address.
- A screenshot of the error message or the login/password reset screen, if applicable.
Run cryoSPARC workflow jobs
Project space selection
A project in cryoSPARC is a high level container corresponding with a project directory on the file system, which stores all associated Jobs of a project. Each project in cryoSPARC is entirely contained within a file system directory. All the jobs and their respective intermediate and output data created within a project will be stored within the project directory.
- When you start a new project in cryoSPARC GUI, please select and use /scratch/gacrc-cryo as the cryoSPARC project space.
- This folder is owned by gacrc-cryo. Regular cryoSPARC users have access and read permissions which allow them to browse files in this folder and copy files from this folder to their own storage spaces on Sapelo2.
Run job on the master node
cryoSPARC will use the master node to run some types of workflow jobs, for example, "Import Movies", "Inspect Picks", and the interactive job "Select 2D Classes". When a job is created, if cryoSPARC will use the master node to run the job, you will be notified about this in cryoSPARC GUI.
Run job using "Lane Sapelo2 Default (cluster)"
- In cryoSPARC, queue a job to "Lane Sapelo2 Default (cluster)"; The job will be dispatched to the worker node via Slurm. Please note, gacrc-cryo, instead of your own Sapelo2 user account, is the user account owning and running the job. We highly recommend you to use this method to run cryoSPARC workflow jobs on Sapelo2.
- cryoSPARC will decide on how many CPU cores and how much memory it will use to run a workflow job, depend on the type of the job and your data size. Currently, we configured that from each worker node cryoSPARC can use up to 20GB memory and 4 CPU cores.
- If the job needs to run on GPU devices, cryoSPARC will queue the job with a default number of GPU devices , for example 1. You can change this number by yourself in cryoSPARC GUI when you create the job. Please note that the maximum number of GPU devices installed on the worker node is 4.
Documentation (v4.0+)
About cryoSPARC: https://guide.cryosparc.com/
Get Started with CryoSPARC: Introductory Tutorial: https://guide.cryosparc.com/processing-data/get-started-with-cryosparc-introductory-tutorial
A Tour of the CryoSPARC Interface: https://guide.cryosparc.com/application-guide-v4.0+/a-tour-of-the-cryosparc-interface
Using the CryoSPARC Interface: https://guide.cryosparc.com/application-guide-v4.0+/using-the-cryosparc-interface
Creating and Running Jobs: https://guide.cryosparc.com/application-guide-v4.0+/creating-and-running-jobs
Tutorial videos: https://guide.cryosparc.com/processing-data/tutorial-videos
Installation
- Version 4.3.1 master is installed on the master node (cryosparc.gacrc.uga.edu).
- Version 4.3.1 workers are installed on one worker GPU node (NVIDIA Tesla A100 GPU node).
System
64-bit Linux