The current GATK version is 3.8-0
Examples: Monday, today, last week, Mar 26, 3/26/04

Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Get notifications!

You can opt in to receive email notifications, for example when your questions get answered or when there are new announcements, by following the instructions given here.

Got a problem?

1. Search using the upper-right search box, e.g. using the error message.
2. Try the latest version of tools.
3. Include tool and Java versions.
4. Tell us whether you are following GATK Best Practices.
5. Include relevant details, e.g. platform, DNA- or RNA-Seq, WES (+capture kit) or WGS (PCR-free or PCR+), paired- or single-end, read length, expected average coverage, somatic data, etc.
6. For tool errors, include the error stacktrace as well as the exact command.
7. For format issues, include the result of running ValidateSamFile for BAMs or ValidateVariants for VCFs.
8. For weird results, include an illustrative example, e.g. attach IGV screenshots according to Article#5484.
9. For a seeming variant that is uncalled, include results of following Article#1235.

Did we ask for a bug report?

Then follow instructions in Article#1894.

Formatting tip!

Wrap blocks of code, error messages and BAM/VCF snippets--especially content with hashes (#)--with lines with three backticks ( ``` ) each to make a code block as demonstrated here.

Jump to another community
Download the latest Picard release at
GATK version 4.beta.3 (i.e. the third beta release) is out. See the GATK4 beta page for download and details.

15bp deletion previously called by GATK v1 not called by GATK 2.0 or 2.1

edited September 2012 in Ask the GATK team

We have a 15bp deletion in a sample that was run on an Illumina sequencer twice:

1) on GAII, 76bp paired-end reads, 10-sample pool;

2) HiSeq2000, 100bp paired-end reads, 24-sample pool.

Both times aligned with bwa and analysed with recommended GATK protocol using the latest available version. The deletion was called both times by GATK 1.0.5083 (76bp batch) and GATK 1.4 (100bp batch). However the deletion is not detected by GATK 2.0 or 2.1-8, either by UnifiedGenotyper or HaplotypeCaller. The newer GATK versions do generate fewer calls and substantially cut out false positives, but on the other hand the sensitivity seems to have dropped too much!
Here is the variant called by the GATK 1.4, 100bp batch:

7   44190538    .   CCCTCCACCCGGCCCA    C   8793.94 PASS    AC=1;AF=0.021;AN=48;BaseQRankSum=14.575;DP=7878;FS=10.160;HRun=0;HaplotypeScore=3737.9770;InbreedingCoeff=-0.0213;MQ=57.74;MQ0=0;MQRankSum=-10.741;QD=29.71;ReadPosRankSum=-0.056   GT:AD:DP:GQ:PL  0/1:216,80:296:99:8794,0,39333

And here it is called by GATK 1.0.5083, 76bp batch:

7   44190538    .   CCCTCCACCCGGCCCA    C   7765.65 PASS    AC=1;AF=0.050;AN=20;DP=1907;Dels=0.02;HRun=1;HaplotypeScore=40.0818;MQ=59.30;MQ0=0;QD=49.78;SB=-1238.06;sumGLbyD=49.78  GT:DP:GQ:PL 0/1:118:99:7766,0,14618

Where is this loss in sensitivity likely to be occurring? Can we adjust any of the default GATK settings to be able to detect these slightly larger indels?
Reads with the 15bp deletion inherently have slightly lower mapping qualities, but I would have thought this is taken into account for indel calling.
(I should add that we have a sample with a 27bp homozygous deletion and this always gets called.)

I'd be happy to send the relevant part of the bam file if that would help.

Thanks, Hana

Post edited by Geraldine_VdAuwera on


Sign In or Register to comment.