Cell Ranger7.0 (latest), printed on 09/29/2022
The cellranger pipeline outputs an indexed BAM file containing position-sorted reads aligned to the genome and transcriptome, as well as unaligned reads. BAM files can be used for troubleshooting reads that were unaligned or converting BAM files back to FASTQ files.
Each read in this BAM file has Chromium cellular and molecular barcode information attached. The following tables assume basic familiarity with the BAM format. The Type column refers to the type of value stored in the tag (see the SAM/BAM standard) documentation for details.
Chromium cellular and molecular barcode information for each read is stored in the following
|Z||Chromium cellular barcode sequence that is error-corrected and confirmed against a list of known-good barcode sequences. For multiplex Fixed RNA Profiling, the cellular barcode is a combination of the 10x GEM Barcode and Probe Barcode sequences.|
|Z||Chromium cellular barcode sequence as reported by the sequencer. For multiplex Fixed RNA Profiling, the cellular barcode is a combination of the 10x GEM Barcode and Probe Barcode sequences.|
|Z||Chromium cellular barcode read quality. For multiplex Fixed RNA Profiling, the cellular barcode is a combination of the 10x GEM Barcode and Probe Barcode sequences. Phred scores as reported by sequencer.|
|Z||Chromium molecular barcode sequence that is error-corrected among other molecular barcodes with the same cellular barcode and gene alignment.|
|Z||Chromium molecular barcode sequence as reported by the sequencer.|
|Z||Chromium molecular barcode read quality. Phred scores as reported by sequencer.|
|Z||Trimmed sequence. For the Single Cell 3' v1 chemistry, this is trailing sequence following the UMI on Read 2. For the Single Cell 3' v2 chemistry, this is trailing sequence following the cell and molecular barcodes on Read 1.|
The cell barcode
CB tag includes a suffix with a dash separator followed by a number:
This number denotes what we call a GEM well, and is used to virtualize barcodes in order to achieve a higher effective barcode diversity when combining samples generated from separate GEM chip channel runs. Normally, this number will be "1" across all barcodes when analyzing a sample generated from a single GEM chip channel. It can either be left in place and treated as part of a unique barcode identifier, or explicitly parsed out to leave only the barcode sequence itself.
The following tags will also be present on reads that mapped to the genome and overlapped an exon by at least one base pair. Reads aligned to the transcriptome across exon junctions in the genome will have a large gap in their CIGAR string i.e., 35M225N64M. A read may align to multiple transcripts and genes, but it is only considered confidently mapped to the transcriptome if it is mapped to a single gene (see this page for methods to check for multi-mapped reads). Cell Ranger modifies MAPQ values; see the MM tag below.
|Z||Present in reads aligned to the same strand as the transcripts in this semicolon-separated list that are compatible with this alignment. Transcripts are specified with the |
|Z|| Present for reads that are aligned to the antisense strand of annotated transcripts. If intron counts are not included (with |
|Z||Semicolon-separated list of gene IDs that are compatible with this alignment. Gene IDs are specified with the |
|Z||Semicolon-separated list of gene names that are compatible with this alignment. Gene names are specified with |
|i||Set to 1 if the genome-aligner (STAR) originally gave a MAPQ < 255 (it multi-mapped to the genome) and Cell Ranger changed it to 255 because the read overlapped exactly one gene.|
|A||Single character indicating the region type of this alignment (E = exonic, N = intronic, I = intergenic).|
|i||The number of poly-A nucleotides trimmed from the 3' end of read 2. Up to 10% mismatches are permitted.|
|Z||For Fixed RNA Profiling, a semicolon-separated list of probe IDs: one probe ID if both read halves align to the same probe, and two probe IDs if each read half aligns to a different probe, or NA if a read half does not align to a probe.|
|i||The number of template switch oligo (TSO) nucleotides trimmed from the 5' end of read 2. Up to 3 mismatches are permitted. The 30-bp TSO sequence is |
|i||Extra alignment flags. The bits of this tag are interpreted as follows: |
Some aspects of the BAM file are particular to Fixed RNA Profiling samples. The mapping quality (MAPQ) values described here do not apply to 3' or 5' Gene Expression data.
A read that multi-maps to the reference transcriptome, but maps uniquely to a single probe, is confidently mapped to that probe and its gene. The mapping quality has the following definition:
||Both read halves map to the same probe.|
||Each read half maps to a different probe.|
||One read half maps to a probe and the other half does not|
||Neither read half maps to a probe|
The BAM tag
pr:Z reports a semicolon-separated list of probe IDs. See above for a detailed description.
Sequencing data passed in as a Feature Barcode library type is not aligned to the genome. The BAM file will contain unaligned records for these reads, with the following tags representing the Feature Barcode sequence extracted from the read, and the feature reference it was matched to, if any. See the Feature Barcode Extraction Pattern section for more details about the alignment algorithm. The BAM read sequence will contain all the bases outside of the cell barcode and UMI regions.
|Z||Chromium Feature Barcode sequence that is error-corrected and confirmed against known Feature Barcode sequences from the feature reference.|
|Z||Chromium Feature Barcode sequence as reported by the sequencer.|
|Z||Chromium Feature Barcode read quality. Phred scores as reported by sequencer.|
|Z||Feature identifier matched to this Feature Barcode read. Specified in the |
This Analysis Guide tutorial walks users through the process of identifying records in the BAM file that contributes to UMI counting: Navigating 10x Genomics Barcoded BAM Files. Note: 10x Genomics does not provide support for community-developed tools and makes no guarantees regarding their function or performance. Please contact tool developers with any questions. If you have feedback about Analysis Guides, please email [email protected]