# 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](../scenarios/public_crispr_yusa.md): Known-good guide-counting lane with count agreement and Edlib validation. - [Public barcode demux: SRP009896 exact-prefix lane](../scenarios/barcode_srp009896_comparator.md): Exact fixed-position barcode demultiplexing with documented Cutadapt and hash baselines. - [Feature barcode assignment: 10x TotalSeq-B public lane](../scenarios/feature_barcode_10x.md): Per-read fixed-window feature-barcode assignment with exact-slice baseline agreement. - [CRISPR guide capture extraction: 10x GEM-X public lane](../scenarios/perturb_seq_10x_guide_capture.md): Single-guide fixed-window guide-capture extraction with exact-slice baseline agreement. - [Amplicon primer-start assignment: ARTIC V3 public lane](../scenarios/amplicon_artic_primer_start.md): Fixed-window primer-start assignment with exact-prefix baseline agreement. - [Oligo/adapter prefix assignment: TruSeq R1 public lane](../scenarios/oligo_adapter_truseq_prefix.md): Fixed-window adapter-prefix assignment with exact-slice baseline agreement. ## Low-confidence inference or weak signal - [Barcode autopsy: weak signal and unsafe rescue](../scenarios/barcode_autopsy_review.md): 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](../scenarios/barcode_wrong_offset_fixture.md): 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](../scenarios/barcode_autopsy_review.md): 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](../scenarios/barcode_unsafe_correction.md): 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](../scenarios/barcode_autopsy_review.md): 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](../scenarios/barcode_wrong_offset_fixture.md): 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](../scenarios/bcl_tiny_classic.md): Classic per-cycle BCL output count-total validation against an available bcl2fastq row.