Cell Ranger2.2, printed on 11/21/2024
Cell Ranger is delivered as a single, self-contained tar file that can be unpacked anywhere on your system. It bundles all of its own required software dependencies, which are pre-compiled to run on a wide range of Linux distributions.
For convenience, the reference data package required for Cell Ranger is provided as a separate download.
Step 1 – Download and unpack the Cell Ranger
file in any location. In this example we use /opt.
$ cd /opt [ download file from downloads page ] $ tar -xzvf cellranger-2.2.0.tar.gz
This unpacks Cell Ranger, its dependencies, and the cellranger script into a new directory called cellranger-2.2.0.
Step 2 – Download and unpack any of the reference data files in a convenient location:
[ download file from downloads page ] $ tar -xzvf refdata-cellranger-vdj-GRCh38-alts-ensembl-2.0.0.tar.gz
This creates a new directory called refdata-cellranger-vdj-GRCh38-alts-ensembl-2.0.0 that contains a single reference (in this case, GRCh38/Ensembl ). Each reference contains a set of pre-generated indices and other data required by Cell Ranger.
Step 3 – Prepend the Cell Ranger directory to your
$PATH. This will allow you to invoke the cellranger
command.
If you unpacked both Cell Ranger and the reference data into /opt, then you would run the following command:
$ export PATH=/opt/cellranger-2.2.0:$PATH
You may wish to add this command to your .bashrc for convenience.
Next, please run the bundled site check script and send the output to 10x. We will review the information to ensure that Cell Ranger will run smoothly once you have generated your own Chromium data. Assuming you have installed Cell Ranger as described above, please run the following commands:
$ cellranger sitecheck > sitecheck.txt $ cellranger upload [email protected] sitecheck.txt
If you plan to run Cell Ranger on a cluster, please run and send us the output twice, once on a submit host and once on a cluster node.
If your system does not have direct Internet connectivity, please send the
output files as attachments to [email protected].
To ensure that the cellranger pipeline is installed correctly, use
cellranger testrun. This test can take up to 60 minutes on a
sixteen-core workstation. Assuming you have installed Cell Ranger into
/opt, the command to run the test would look like:
$ export PATH=/opt/cellranger-2.2.0:$PATH $ cellranger testrun --id=tiny cellranger testrun 2.2.0 Copyright (c) 2016 10x Genomics, Inc. All rights reserved. ----------------------------------------------------------------------------- Martian Runtime - v2.3.3 Running preflight checks (please wait)... 2016-11-14 09:57:51 [runtime] (ready) ID.tiny.SC_RNA_COUNTER_CS.SC_RNA_COUNTER.SETUP_CHUNKS 2016-11-14 09:57:54 [runtime] (split_complete) ID.tiny.SC_RNA_COUNTER_CS.SC_RNA_COUNTER.SETUP_CHUNKS ... Pipestance completed successfully!
Whether the test pipestance succeeds or fails, you will then see:
Saving diagnostics to tiny/tiny.mri.tgz
This tiny.mri.tgz file contains diagnostic information 10x can use
to help resolve any problems. It is generated whether the pipeline succeeds or
fails. If the pipeline fails and you need troubleshooting assistance, you can
send this file directly to us from the command line:
$ cellranger upload [email protected] tiny/tiny.mri.tgz
If your system does not have direct Internet connectivity, you can also send the
file as an attachment to [email protected].