There are three primary ways to run Space Ranger:
- Single server: Space Ranger can run directly on a dedicated server. This is the most straightforward approach and the easiest to troubleshoot.
- Job submission mode: Space Ranger can run using a single node on the cluster. Less cluster coordination is required since all work is done on the same node. This method works well even with job schedulers that are not officially supported.
- Cluster mode: Space Ranger can run using multiple nodes on the cluster. This method provides high performance but is difficult to troubleshoot since cluster setup varies among institutions.
Recommendations and requirements, in order of computational speed (left to right):
|Job Submission Mode
|Organizations using an HPC with SGE or LSF for job scheduling
|Organizations using an HPC
|Users without access to an HPC
|Splits each analysis across multiple compute nodes to decrease run time
|Runs each analysis on a single compute node
|Runs each analysis directly on a dedicated server
|HPC with SGE or LSF for job scheduling
|HPC with most job schedulers
|Linux computer with minimum 8 cores & 64 GB RAM
The majority of the information on this website uses the single server approach. Follow the instructions below to analyze a 10x Genomics library:
- Generating FASTQs
- Specifying input FASTQs
- Single-library analysis
Space Ranger can be run in job submission mode, by treating a single node from the cluster like a local server. This leverages existing institutional hardware for pipeline analysis.
This mode of operation is what most people have in mind when it comes to working with clusters. A large computational job is submitted to the cluster and there is one job ID to track during job execution.
Space Ranger can be run in cluster mode, using SGE or LSF to run the stages on multiple nodes via batch scheduling. This allows highly parallel stages to utilize hundreds or thousands of cores concurrently, dramatically reducing time to solution.
Instead of submitting one job to the cluster, Space Ranger creates hundreds, and potentially thousands, of small stage jobs. Each of these stage jobs needs to be queued, launched, and tracked by the pipeline framework. The necessary coordination between Space Ranger and the cluster makes this approach harder to set up and troubleshoot, since every cluster configuration is different.