10x Genomics
Chromium Single Cell Gene Expression

Cell Ranger6.0, printed on 12/21/2024

Feature Barcode Analysis

Cell Ranger processes all Feature Barcode data through a counting pipeline that quantifies each feature in each cell. This analysis is done by the cellranger count pipeline. The pipeline outputs a unified feature-barcode matrix that contains gene expression counts alongside Feature Barcode counts for each cell barcode. The feature-barcode matrix replaces the gene-barcode matrix emitted by older versions of Cell Ranger.

The pipeline first extracts and corrects the cell barcode and UMI from the feature library using the same methods as gene expression read processing. It then then matches the Feature Barcode read against the list of features declared in the Feature Barcode Reference. The counts for each feature are available in the feature-barcode matrix output files and in the Loupe Browser output file.

To enable Feature Barcode analysis, cellranger count needs two new inputs:

• Libraries CSV is passed to cellranger count with the --libraries flag, and declares the FASTQ files and library type for each input dataset. In a typical Feature Barcode analysis there will be two input libraries: one for the normal single-cell gene expression reads, and one for the Feature Barcode reads. This argument replaces the --fastqs argument.
• Feature Reference CSV is passed to cellranger count with the --feature-ref flag and declares the set of Feature Barcode reagents in use in the experiment. For each unique Feature Barcode used, this file declares a feature name and identifier, the unique Feature Barcode sequence associated with this reagent, and a pattern indicating how to extract the Feature Barcode sequence from the read sequence. See Feature Barcode Reference for details on how to construct the feature reference.

After creating the CSV files, run cellranger count:

$ cd /home/jdoe/runs
$ cellranger count --id=sample345 \
                   --libraries=library.csv \
                   --transcriptome=/opt/refdata-gex-GRCh38-2020-A \
                   --feature-ref=feature_ref.csv \
                   --expect-cells=1000

The complete set of arguments to cellranger count are covered in Single-Sample Analysis.

Feature and Library Types

When inputting Feature Barcode data to Cell Ranger via the Libraries CSV File, you must declare the library_type of each library. Specific values for library_type will enable additional downstream processing, specifically for CRISPR Guide Capture and Antibody Capture. The following table outlines the types of libraries that can be specified and what they mean for the downstream processing.

Libraries CSV File

The Libraries CSV File declares the input FASTQ data for the libraries that make up a Feature Barcode experiment. This will include one library containing Single Cell Gene Expression reads, and one or more libraries containing Feature Barcode reads. To use cellranger count in Feature Barcode mode, you must create a Libraries CSV File and pass it with the --libraries flag. The following table describes what the content should be in the Libraries CSV File.

Example Libraries CSV Files

Gene expression + CRISPR libraries. In this example we've demultiplexed the sequencing data from two libraries named GEX_sample1 and CRISPR_sample1 on the bcl2fastq / mkfastq sample sheet. This generated FASTQ files named GEX_sample1_S0_L001_001.fastq.gz and CRISPR_sample1_S0_L001_001.fastq.gz into the path /opt/foo. We pass the FASTQ sample names and paths to Cell Ranger with the appropriate library types:

Gene expression + Antibody libraries. In this example we've demultiplexed the sequencing data from two libraries named GEX_sample2 and Ab_sample2 on the bcl2fastq / mkfastq sample sheet. This generated FASTQ files named GEX_sample2_S0_L001_001.fastq.gz and Ab_sample2_S0_L001_001.fastq.gz into the path /opt/foo. We pass the FASTQ sample names to Cell Ranger with the appropriate library types:

Using Multiple Library Types

If your assay scheme creates a library containing multiple library_types, for example if you're using CRISPR Guide Capture and Antibody Capture features, you will need to select a single library_type for the library when inputting it into the Libraries CSV File. This will provide only one kind of specialized library analysis. To get multiple specialized analyses, you will need to run Cell Ranger multiple times, passing different library_type values in the Libraries CSV File. This is a limitation of Cell Ranger that will be ameliorated in a future release. Regardless of the library_type specified, the feature-barcode matrix outputs will contain counts for all specified features.

Feature Reference CSV File

A Feature Reference CSV File is required when processing Feature Barcode data. It declares the molecule structure and unique Feature Barcode sequence of each feature present in your experiment. Each line of the CSV declares one unique Feature Barcode. The Feature Reference CSV File is passed to cellranger count with the --feature-ref flag. Please note that the CSV may not contain characters outside of the ASCII range.

Targeted Gene Expression data is compatible with Feature Barcode analysis. However, if Targeted Gene Expression data is analyzed in conjunction with CRISPR-based Feature Barcode data, there are additional requirements imposed for the Feature Reference CSV file. Specifically, any CRISPR guide RNA target genes (in the target_gene_id column of the Feature Reference CSV file) must correspond to genes which are also included in the targeted gene expression Target Panel CSV file (in the gene_id column).

This table describes the columns in the Feature Reference CSV File. Example files can be found below.

Feature Barcode Extraction Pattern

The pattern field of the feature reference defines how to locate the Feature Barcode within a read. The Feature Barcode may appear at a known offset with respect to the start or end of the read or may appear at a fixed position relative to a known anchor sequence. The pattern column can be made up of a combination of these elements:

• 5P: denotes the beginning of the read sequence. May appear 0 or 1 times, and must be at the beginning of the pattern. Only 5P or 3P may appear, not both. (^ may be used instead of 5P.)
• 3P: denotes the end of the read sequence. May appear 0 or 1 times, and must be at the end of the pattern. ($ may be used instead of 3P.)
• N: denotes an arbitrary base.
• A, C, G, T: denotes a fixed base that must match the read sequence exactly.
• (BC): denotes the Feature Barcode sequence as specified in the sequence column of the feature reference. Must appear exactly once in the pattern.

Any constant sequences made up of A, C, G and T in the pattern must match exactly in the read sequence. Any N in the pattern is allowed to match a single arbitrary base. A modest number of fixed bases should be used to minimize the chance of a sequencing error disrupting the match. The fixed sequence should also be long enough to uniquely identify the position of the Feature Barcode. For feature types that require an non-N anchor, we recommend 12bp-20bp of constant sequence. The extracted Feature Barcode sequences are corrected up to a Hamming distance of 1 using the 10x barcode correction algorithm that is used to correct cell barcodes.

Antibody Capture with TotalSeq™-B

TotalSeq™-B is a line of antibody-oligonucleotide conjugates supplied by BioLegend that are compatible with the Single Cell 3' v3 assay. The Feature Barcode sequence appears at a fixed position (base 10) in the R2 read.

Dataset Example
Example TotalSeq™-B Feature Reference CSV Please note, this is a pre-release set of TotalSeq-B antibodies. The Feature Barcode sequences have since changed. Please refer to https://www.biolegend.com/totalseq for the latest conjugated Feature Barcode information.

Antibody Capture with TotalSeq™-C

TotalSeq™-C is a line of antibody-oligonucleotide conjugates supplied by BioLegend that are compatible with the Single Cell 5' assay. The Feature Barcode sequence appears at a fixed position (base 10) in the R2 read.

Dataset Example
Example TotalSeq™-C Feature Reference CSV

The feature reference for Immudex's dMHC Dextramer® libraries with dCODE Dextramers has the same feature barcode pattern as TotalSeq™-C. Use "Antibody Capture" in the feature_type column for dextramer or multimer reagents. Therefore, the same feature reference example for TotalSeq™-C can also be used for MHC Dextramer® libraries.

Antibody Capture for TotalSeq™-A

TotalSeq™-A is a line of antibody-oligonucleotide conjugates supplied by BioLegend that are compatible with the Single Cell 3' v2 and Single Cell 3' v3 kits. The Feature Barcode sequence appears at the start of the R2 read.

Although TotalSeq™-A can be used with the CITE-Seq assay, CITE-Seq is not a 10x supported assay. Please contact New York Genome Center or BioLegend for assistance with the assay or software.

Example TotalSeq™-A Feature Reference CSV

CRISPR Guide Capture

In CRISPR Guide Capture assays, the Feature Barcode sequence is the CRISPR protospacer sequence. The protospacer is followed by a downstream constant sequence in the guide RNA which is used as an anchor to identify the location of the protospacer. We recommend using a 12bp-20bp constant sequence that can be uniquely identified, but is short enough that it is unlikely to be disrupted by a sequencing error. In the example Feature Reference CSV file we declare six guide RNA features with six distinct barcode / protospacer sequences. We use the target_gene_id and target_gene_name columns to declare the target gene of each guide RNA, for use in downstream CRISPR perturbation analysis. Two guides are declared with target_gene_id as Non-Targeting. Cells containing Non-Targeting guides will be used as controls for CRISPR perturbation analysis. The four remaining guides target two genes.

Example CRISPR Feature Reference CSV