Zubair Khalid

Virologist/Molecular Biologist | Veterinarian | Bioinformatician

Conventional & Molecular Virology • Vaccine Development • Computational Biology

Dr. Zubair Khalid is a veterinarian and virologist specializing in conventional and molecular virology, vaccine development, and computational biology. Dedicated to advancing animal health through innovative research and multi-omics approaches.

Dr. Zubair Khalid - Veterinarian, Virologist, and Vaccine Development Researcher specializing in Computational Biology, Multi-omics, Animal Health, and Infectious Disease Research

Category: Guides

Haplotype Based Variant Detection From Short Read Sequencing

This guide explains how haplotype based variant detection uses local de novo assembly of short reads to identify phased variants. It is intended for bioinformaticians, clinical researchers, and students who need a practical framework for short read variant calling. The method differs from simple pileup approaches by accounting for the haplotype context of each read, improving accuracy in complex regions. You can explore foundational concepts in the EMBL EBI Training materials on variant analysis.

Haplotype based detection reconstructs short genomic segments directly from the reads, then compares these assembled haplotypes to the reference. This approach can distinguish variants that occur on the same chromosome copy (in cis) from those on different copies (in trans). For example, when two heterozygous variants are close together, accurate phasing matters for interpreting compound heterozygosity. The Galaxy Training Network offers practical tutorials on running haplotype caller tools within reproducible workflows.


At a Glance

Aspect Key Points
Core principle Local de novo assembly of short reads into candidate haplotypes, then realignment to detect and phase variants.
Typical tools GATK HaplotypeCaller, FreeBayes, Octopus, DeepVariant (with phasing module).
Input data Paired end short read FASTQ files or aligned BAM files, reference genome in FASTA format.
Output VCF file with phased genotypes (GT field), often with haplotype blocks and phase quality scores.
Strengths Better sensitivity for indels, ability to phase nearby variants, reduced reference bias compared to pileup.
Limitations Computationally intensive, struggles with long repeats or highly repetitive regions, limited phasing distance (usually a few hundred bases to a few kilobases).

Use this table to quickly gauge whether haplotype based detection matches your analysis goals. The NCBI Bookshelf chapter on sequence variant analysis provides a deeper overview of these tradeoffs.


Decision Criteria

Choose haplotype based detection when your primary goal includes phasing variants within a read length or detecting small insertions and deletions that pileup methods often miss. The method is preferable for diploid or polyploid organisms where haplotype specific effects matter. For example, in cancer genomics, distinguishing somatic variants on the same or different alleles can affect interpretation of compound mutations. According to the Bioconductor documentation on variant tools, the main decision factors are:

  • Read length and coverage: Haplotype assembly requires sufficient overlapping reads (typically at least 10x to 20x depth). Shorter reads (e.g., 75 bp) limit phasing range but still enable local assembly.
  • Ploidy: Set the ploidy parameter correctly. Most mammalian analyses use diploid mode, but experiments with aneuploidy or pooled microbial samples need adjusted ploidy.
  • Region complexity: In segmental duplications or paralogous gene families, haplotype based methods may still miscall due to ambiguous read mapping. The HiFi sequencing accurately identifies clinically relevant variants in paralogous genes study shows that short reads alone often fail in such regions, so consider long read validation.

If you only need simple SNP detection in homogeneous, low complexity regions with no phasing requirement, a pileup caller (e.g., BCFtools mpileup) may be faster and adequate.


Practical Workflow

The following stepwise process outlines a typical haplotype based variant detection pipeline. This workflow is adapted from resources in the Galaxy Training Network and the EMBL EBI Training short read analysis materials.

1. Quality Control and Trimming

Start with raw FASTQ files. Run FastQC or a similar tool to assess quality, adapter contamination, and GC bias. Trim low quality bases and adapter sequences using cutadapt or Trimmomatic. Poor quality reads inflate false positive variant calls.

2. Alignment to Reference Genome

Align trimmed reads to a reference genome with a splice aware aligner for RNAseq or a DNA aligner like BWA MEM. Produce coordinate sorted BAM files. Ensure the reference is the same version used for subsequent tools. The NCBI Sequence Read Archive provides example datasets for practice.

3. Duplicate Marking

Mark PCR or optical duplicates using Picard MarkDuplicates or SAMtools. Duplicate reads are identical copies that can be incorrectly counted as multiple independent observations, biasing variant frequency. This step is critical for accurate haplotype frequency estimates.

4. Base Quality Score Recalibration (BQSR)

Apply base quality score recalibration with GATK BaseRecalibrator. This step empirically adjusts base quality scores based on covariates (e.g., read group, machine cycle). BQSR reduces systematic errors and improves variant calling accuracy, especially for base quality sensitive haplotype assembly.

5. Haplotype Calling

Run the haplotype caller (e.g., GATK HaplotypeCaller) on recalibrated BAM files. The algorithm performs local de novo assembly in each active region, evaluates candidate haplotypes against reads, and calculates genotype likelihoods. For germline variant detection, use the GVCF mode for joint genotyping across multiple samples. Set the ploidy to the expected value (2 for human germline). The Not Missing the Notch: Detection Challenges of Juxtamembrane NOTCH1 Variant Detection in T Cell Acute Lymphoblastic Leukemia report highlights that even with assembly, some regions remain difficult and require manual inspection or alternative methods.

6. Joint Genotyping (Optional)

If you processed samples with GVCF mode, combine them using GenomicsDBImport and then run GenotypeGVCFs. Joint genotyping leverages population information to improve variant quality scores for rare variants.

7. Variant Filtration

Apply hard filters based on the GATK recommended parameters (e.g., QD < 2.0, FS > 60.0, MQ < 40.0) or use VQSR (Variant Quality Score Recalibration) with training data. Always check transition transversion ratio and other metrics to gauge filter effectiveness.

8. Phasing Information

Most haplotype callers output phasing information in the VCF format, expressed as phase sets (PS) or through the GT field. For longer range phasing, consider tools like WhatsHap or SHAPEIT, though these require additional sequencing data or known haplotype information.

Follow this workflow iteratively: review output metrics, adjust parameters, and re run if needed.


Common Mistakes

Avoid these pitfalls that frequently compromise haplotype based variant detection.

  • Using default ploidy for non diploid samples. For pooled samples or aneuploid cells, the default diploid mode underestimates or overestimates allele frequencies. Always specify the correct ploidy.
  • Skipping duplicate removal. Unmarked duplicates inflate coverage and reduce confidence in variant allele frequencies. The Benchmarking within sample minority variant detection with short read sequencing in M. tuberculosis study demonstrates that duplicate bias can obscure low frequency variants.
  • Ignoring base quality scores. Assembly algorithms depend on per base qualities. If base quality calibration is omitted, false positive calls may dominate results.
  • Failing to account for strand bias. Variants supported exclusively by one strand orientation are often artifacts. Use the FS or SB annotations to filter them.
  • Using an incorrect reference genome version. Mixing references (e.g., GRCh37 vs. GRCh38) leads to mismapped reads and inaccurate variant calls.

Limits and Uncertainty

No variant detection method is perfect. Haplotype based approaches have specific limitations that you must acknowledge when interpreting results.

  • Repetitive regions. Short reads cannot resolve repeats longer than the read length. In tandem repeats or segmental duplications, variant calls may be unreliable. The Not Missing the Notch paper highlights how juxtamembrane regions in NOTCH1 are prone to false negatives with short read sequencing alone.
  • Paralogous sequence confusion. Reads from highly similar gene copies can be assigned to the wrong copy, leading to erroneous phasing. The HiFi sequencing accurately identifies clinically relevant variants in paralogous genes study notes that short read haplotype calling cannot reliably separate variants in such families without additional pedigree or long read data.
  • Limited phasing distance. Haplotype blocks constructed from read pairs typically extend only a few hundred bases. For phasing across entire genes, you need linked read, long read, or trio data. The Ultraaccurate genome sequencing and haplotyping of single human cells approach achieves full chromosome phasing but uses specialized library preparation.
  • Minority variant detection. In mixed samples (e.g., tumor biopsies or microbial populations), very low frequency variants may be missed. The Benchmarking within sample minority variant detection analysis shows that sensitivity drops below 5% variant allele frequency, especially without targeted deep sequencing.
  • Computational cost. Haplotype assembly is resource intensive. Large genomes or whole exome datasets can require hundreds of gigabytes of RAM and hours of runtime.

When reporting results, always note the coverage depth, read length, and any known problematic regions. Do not interpret missing calls in complex regions as evidence of absence.


Frequently Asked Questions

1. What is the main difference between haplotype based and pileup based variant calling?

Haplotype based calling reassembles read sequences locally to produce candidate variants, then aligns reads back to those haplotypes. Pileup methods simply compare each read base to the reference at a given position. Haplotype methods are more sensitive to indels and can phase nearby variants. For more details, see the NCBI Bookshelf comparison of calling algorithms.

2. Can haplotype based methods detect structural variants?

Standard haplotype callers are optimized for small variants (SNPs and indels) within a few hundred bases. They may signal large deletions or insertions through abnormal read pairs or split reads, but they are not designed for structural variant detection. Dedicated tools like Manta or Delly are better for large events. However, haplotype aware assembly can sometimes recover complex small scale structural changes.

3. How does sequencing coverage affect haplotype accuracy?

Coverage below 10x yields insufficient reads for reliable local assembly, increasing false negatives. Optimal depth is 30x for diploid genome calling. At very high coverage (greater than 100x), haplotype calling may still be accurate, but duplicates and PCR bias become more problematic. Always mark duplicates and down sample if needed.

4. What is the role of base quality scores in haplotype assembly?

Base quality scores directly influence the likelihood calculation during assembly and genotyping. Overly optimistic base qualities cause false positives, while conservative qualities reduce sensitivity. Recalibration using known variant sites (e.g., dbSNP) improves score accuracy. The Bioconductor package QualityScaler and GATK documentation provide guidance on recalibration.


References and Further Reading


Related Articles