HOME  ›   pipelines
If your question is not answered here, please email us at:  ${email.software}

10x Genomics
Chromium Single Cell Immune Profiling

Clonotype Grouping

Table of contents

Clonotype grouping overview

workflow

During the clonotype grouping stage, cell barcodes are placed in groups called clonotypes. Each clonotype consists of all descendants of a single, fully rearranged common ancestor, as approximated computationally. During this process, some cell barcodes are flagged as likely artifacts and filtered out, meaning that they are no longer called as cells.

T cells: The lack of somatic hypermutation in T cell receptors (TCRs) yields biological clonotypes which have identical V(D)J transcripts. Technical artifacts (e.g. arising in reverse transcription) can result in the computed clonotypes having isolated differences. These are generally rare.

B cells: Fully rearranged B cell receptors (BCRs) can undergo somatic hypermutation (SHM), which can increase antigen affinity. Thus for BCRs, V(D)J transcripts in a clonotype can differ at any position, as shown below:

Because SHM can introduce numerous mutations, it is challenging to accurately infer B cell clonotypes. Cell Ranger v5.0 and above accomplishes this by invoking a module for clonal analysis called enclone, which simultaneously groups cells into clonotypes and filters some out.

enclone is also available in beta as a separate command-line, fast, exploratory tool, see https://10xgenomics.github.io/enclone or bit.ly/enclone. The command line form has arguments permitting granular control over the clonotyping and filtering heuristics. enclone can also display clonotypes and infer phylogenetic trees. enclone as a command-line tool is frequently updated and supported via [email protected], separate from Cell Ranger.

Brief description of clonotype grouping in enclone

Clonotype grouping and the associated filtering are complex and heuristic. The concepts are described briefly here, and some link out to the enclone site for technical documentation.

Clonotype grouping

This includes two key steps:

Step 1: Cells are placed into groupings called exact subclonotypes if they have identical V(D)J transcripts. The transcript sequences must be identical from the start codon through the J gene, and the constant region gene assignments must be the same. The algorithm does not test for somatic hypermutations (SHM) in the 5’-UTR or constant region.

Step 2: Only productive transcripts are used. Cells which are missing a chain (likely due to low coverage) are placed in their own exact subclonotype. They may later be joined into the clonotype with which they share a chain type.

Exact clonotypes are iteratively merged into clonotypes based on comparing each pair of exact subclonotypes to each other. They can be merged into a single clonotype based on two types of evidence:

(a) Similarity of their rearrangement junction regions. Somatic hypermutation during clonal evolution can cause junction regions to diverge.

(b) Evidence of shared SHM outside their junction regions. This is assessed by identifying positions within V genes that are identical on the two exact subclonotypes, differ from the reference, and do not represent germline differences. An outline of how this is implemented is described on the enclone site.

B. Cell filtering during the clonotype grouping process

During library generation, artifacts can arise by two mechanisms:

(a) Reverse transcription or sequencing can introduce base call errors. These usually occur at bases having low quality scores. Cells with these low quality bases are screened out, typically at a low rate.

(b) GEMs may contain material from two or more cells: entire intact cells, cell fragments, or individual mRNA molecules. Contamination detection is a complex task and is accomplished via multiple heuristic filters. A partial guide to filters can be found on the enclone website. Note that if the multi pipeline is run with both gene expression and V(D)J data, barcodes which are not called cells by the gene expression pipeline will also be deleted from the V(D)J cell set. Refer to the cellranger multi pipeline page to learn about when and why to use the multi pipeline to process V(D)J libraries.

Next steps