Both GATK4 HaplotypeCaller and deep learning-based variant callers identify germline variants in whole-genome sequencing data. The choice between them is consequential — not because one is categorically better, but because their performance profiles differ in ways that are clinically and scientifically relevant depending on your application.

Two Paradigms

GATK4 HaplotypeCaller is a heuristic-probabilistic method built around local de novo assembly of haplotypes at candidate variant sites, followed by genotyping using a read-likelihood model. It has been refined over more than a decade of development by a large community, is deeply embedded in clinical genomics workflows, and produces output that includes the metadata and calibration information that downstream tools in the GATK ecosystem expect.

Deep learning variant callers learn to call variants directly from read pileup images, training on large datasets of sequencing data with known ground truth. They do not make explicit assumptions about the read-likelihood model — instead, the model learns the mapping from pileup to variant call from data.

Where GATK4 Excels

GATK4 performs consistently across a wide range of sequencing platforms and library preparation protocols. Its joint genotyping mode (GVCF-based) scales to cohort sizes of thousands and is the standard approach for population genomics and large-scale biobank analysis. Its variant quality score recalibration (VQSR) framework produces well-calibrated variant calls for common variant types when a high-quality training set is available. For germline SNP and indel calling in standard Illumina data at 30× or greater coverage, GATK4 is the established benchmark.

Where Deep Learning Callers Win

Deep learning methods show particular advantages in non-standard data types: lower coverage sequencing, long-read data from Oxford Nanopore or PacBio platforms, FFPE-degraded samples where oxidative damage artifacts are common, and highly repetitive regions where heuristic assembly struggles. For clinical sequencing programs that regularly encounter these data types, the performance advantages in these regimes are meaningful.

"The choice of variant caller is not a one-time decision — it should be re-evaluated when the sequencing technology, coverage depth, or clinical application changes."

Further reading: GATK documentation (Broad Institute), DeepVariant on GitHub (Google), nf-core/sarek WGS pipeline, and Poplin et al. 2018 — DeepVariant in Nature Biotechnology.

How BioMate helps

BioMate supports both approaches, selects the appropriate caller based on the data type and application specified, and applies the relevant QC profile to the output — so the choice of tool is made explicitly and documented, not defaulted to whatever was installed on the cluster.