DotMatch Report Examples

These examples show what DotMatch reports look like under common run conditions. Use them to compare a new run against a known-good lane or a known failure pattern.

Known-good public data

Public CRISPR guide counting: Yusa/MAGeCK lane: Known-good guide-counting lane with count agreement and Edlib validation.
Public barcode demux: SRP009896 exact-prefix lane: Exact fixed-position barcode demultiplexing with documented Cutadapt and hash baselines.
Feature barcode assignment: 10x TotalSeq-B public lane: Per-read fixed-window feature-barcode assignment with exact-slice baseline agreement.
CRISPR guide capture extraction: 10x GEM-X public lane: Single-guide fixed-window guide-capture extraction with exact-slice baseline agreement.
Amplicon primer-start assignment: ARTIC V3 public lane: Fixed-window primer-start assignment with exact-prefix baseline agreement.
Oligo/adapter prefix assignment: TruSeq R1 public lane: Fixed-window adapter-prefix assignment with exact-slice baseline agreement.

Low-confidence inference or weak signal

Barcode autopsy: weak signal and unsafe rescue: A review-status run with low-confidence offset evidence, low assignment rate, high ambiguity, and unsafe one-edit correction.

Wrong offset or wrong fixed window

Barcode failure fixture: wrong offset and invalid windows: Deliberately constructed reads show wrong offset, invalid window, reverse-complement candidate, and low-complexity failure modes.

Unsafe one-edit correction

Barcode autopsy: weak signal and unsafe rescue: A review-status run with low-confidence offset evidence, low assignment rate, high ambiguity, and unsafe one-edit correction.
Barcode failure fixture: unsafe one-edit correction: Observed barcode sequences are within one edit of multiple targets, so k=1 rescue is unsafe.

Many unmatched or ambiguous reads

Barcode autopsy: weak signal and unsafe rescue: A review-status run with low-confidence offset evidence, low assignment rate, high ambiguity, and unsafe one-edit correction.
Barcode failure fixture: wrong offset and invalid windows: Deliberately constructed reads show wrong offset, invalid window, reverse-complement candidate, and low-complexity failure modes.

Narrow parser milestone

Classic BCL parser milestone: 10x tiny-BCL lane: Classic per-cycle BCL output count-total validation against an available bcl2fastq row.