strkit 0.8.0a10

A toolkit for analyzing variation in short(ish) tandem repeats.

STRkit

A genotyping and analysis toolkit for short(ish) tandem repeats.

© David Lougheed 2021-2023 (versions up to and including 0.8.0a1).

© David Lougheed 2021-2023 & McGill University 2023 (versions beyond 0.8.0a1).

Installation

STRkit requires Python 3.9+ and can be installed from PyPI via pip with the following command:

python -m pip install strkit

For the faster orjson library for JSON parsing and serialization, specify the rustdeps extra:

python -m pip install strkit[rustdeps]

On some Alliance (DRAC/CC) clusters, this will require loading Rust first:

module load rust
python -m pip install strkit[rustdeps]

Commands

strkit call: Genotype caller with bootstrapped confidence intervals

A Gaussian mixture model tandem repeat genotype caller for long read data. STRkit is tuned specifically for high-fidelity long reads, although other long read data should still work.

Features:

• Performant, vectorized (thanks to parasail) estimates of repeat counts from high-fidelity long reads and a supplied catalog of TR loci and motifs.
• Re-weighting of longer reads, to compensate for their lower likelihood of observation.
  • Whole-genome and targeted genotyping modes to adjust this re-weighting.
• Parallelized for faster computing on clusters and for ad-hoc fast analysis of single samples.
• 95% confidence intervals on calls via a user-configurable optional parametric bootstrapping process.

Usage:

strkit call \
  path/to/read/file.bam \  # [REQUIRED] At least one indexed read file (BAM/CRAM)
  --hq \  # If using PacBio HiFi reads, enable this to get better genotyping & more robust expansion detection
  --realign \  # If using PacBio HiFi reads, enable this to enable local realignment / read recovery
  --ref path/to/reference.fa.gz \  # [REQUIRED] Indexed FASTA-formatted reference genome
  --loci path/to/loci.bed \  # [REQUIRED] TRF-formatted (or 4-col, with motif as last column) list of loci to genotype
  --min-reads 4 \  # Minimum number of supporting reads needed to make a call
  --min-allele-reads 2 \  # Minimum number of supporting reads needed to call a specific allele size 
  --flank-size 70 \  # Size of the flanking region to use on either side of a region to properly anchor reads
  --seed 183  # Fixed random number generator seed for replicability

Ideally, you should be using a read file aligned with parameters tuned for tandem repeats. PacBio provides a recommended workflow for CCS alignment in this scenario.

If you're using HiFi reads as input, use the --hq and --realign options to get better genotype calculation and a greater proportion of reads incorporated into the computed genotypes, respectively. These should not add much performance overhead.

If more than one read file is specified, the reads will be pooled. This can come in handy if you have e.g. multiple flow cells of the same sample split into different BAM files, or the reads are split by chromosome.

If you want to output a full call report, you can use the --json output-file.json argument to specify a path to output a more detailed JSON document to. This document contains 99% CIs, peak labels, and some other information that isn't included in the normal TSV file. If you want this file to be indented and human-readable, use the --indent-json flag in addition to --json ....

See the 'Caller catalog format & choosing a catalog' page for more on how to format a locus catalog or choose from existing available catalogs.

Note that the reference genome must be BGZipped and indexed using samtools faidx:

# Starting from a .fa:
bgzip my-reference.fa  # Replaces .fa with a .fa.gz file
samtools faidx my-reference.fa.gz  # Generates a .fai index file

Note on OpenMP Threading

Slow performance can result from running strkit call or strkit re-call on a system with OpenMP, due to a misguided attempt at multithreading under the hood somewhere in Numpy/Scipy (which doesn't work here due to repeated initializations of the Gaussian mixture model.) To fix this, the following environment variable is auto-set (hardcoded) before running:

export OMP_NUM_THREADS=1

If this hard-coded value interferes with your use case, please open an issue.

Further documentation on the STRkit caller:

• Advanced caller usage and configuration
• Caller catalog format & choosing a catalog

strkit visualize: Call visualizer

STRkit bundles a call visualization tool which takes as input a BAM file and a JSON call file from using the --json flag with strkit call.

It starts a web server on your local machine; the visualizations can be interacted with in a web browser.

To use the tool, run the following command:

strkit visualize path/to/my-alignment.bam \ 
  --ref hg38 \  # or hg19
  --json path/to/my-calls.json \
  -i 1  # 1-indexed offset in JSON file for locus of interest. Default is 1 if left out.

This will output something like the following:

 * Serving Flask app 'strkit.viz.server' (lazy loading)
 * Environment: production
   WARNING: This is a development server. Do not use it in a production deployment.
   Use a production WSGI server instead.
 * Debug mode: on
 * Running on http://localhost:5011 (Press CTRL+C to quit)
...

You can then go to the URL listed, http://localhost:5011, on your local machine to see the visualization tool:

STRkit browser histogram, showing an expansion in the HTT gene.

The same expansion, shown in the igv.js browser. Note the insertions on the left-hand side in most reads, and the heterozygous copy number pattern.

To exit the tool, press Ctrl-C in your command line window as mentioned in the start-up instructions.

strkit re-call: Genotype re-caller

This command has a similar feature-set as strkit call, but is designed to be used with the output of other long-read STR genotyping methods to refine the genotype estimates when calling from HiFi reads.\

Features:

• Support for re-calling output from tandem-genotypes, RepeatHMM, and Straglr
• Strand resampling / bias correction (for use with the tandem-genotypes program)
• 95% confidence intervals on calls via user-configurable bootstrapping

Notes:

• --min-allele-reads will affect the confidence intervals given by the bootstrap process, especially in low-coverage loci. This should be set depending on the read technology being used; something like a single PacBio HiFi read generally contains higher-quality information than a single PacBio CLR read, for example.

strkit mi: Mendelian inheritance analysis

Using trio data, candidate de novo STR mutations (or genotyping errors/dropout rates) can be discovered by looking at inheritance patterns. This tool provides a few different ways to do this, via:

• Mendelian inheritance % (MI) calculations for many common TR genotyping tools for both long/short reads, including support for genotyping methods which report confidence intervals.
• Reports of loci (potentially of interest) which do not respect MI
• An optional test flag to detect de novo events and assign a p-value in trio JSON reports generated by strkit call. Note that this currently will over-report significance with low coverage as tested with the x2 chi-squared test option.

For more information on what kind of analyses can be done with this data, see the Trio analyses with STRkit page.

Copyright and License

Some exclusions to this license apply; specifically portions of strkit/viz/templates/browser.html and files in the catalogs directory.

© David Lougheed 2021-2023 (versions up to and including 0.8.0a1).

© David Lougheed 2021-2023 & McGill University 2023 (versions beyond 0.8.0a1).

Portions of viz/templates/browser.html copyright (C) 2021-2022 Observable, Inc. Used under the terms of the ISC license.

Notice

This program is free software: you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation, either version 3 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program. If not, see https://www.gnu.org/licenses/.