The current GATK version is 3.7-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!

#### ☞ Did you remember to?

1. Search using the upper-right search box, e.g. using the error message.
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.

#### ☞ Formatting tip!

Surround blocks of code, error messages and BAM/VCF snippets--especially content with hashes (#)--with lines with three backticks (  ) each to make a code block.
GATK 3.7 is here! Be sure to read the Version Highlights and optionally the full Release Notes.

# haplotypecaller indel format

Member Posts: 31
edited September 2012

Hi there,
I've done with a run of HaplotypeCaller on my samples. I'm now analysing everything with snpEff, although I'm doing this "outside" GATK. I had to stop the analysis because a huge number of errors, all dealing with indels, such as:

Error while processing VCF entry (line 580649) :
chr21   26718345    .   TAATCCTGAGTTTAA TATCCTAAATGTTTAC    943.26  […]
java.lang.RuntimeException: Insertion '-A+AT' does not start with '+'. This should never happen!
chr21   35260360    .   CATAACAGTTCAT   AGAGACAGAG  425.22  […]
java.lang.RuntimeException: Deletion '+G-TTC' does not start with '-'. This should never happen!


Of course, this is a snpEff error, nevertheless the Indel format looks quite different from what I've ever seen. Consider the first line above: shouldn't it be like

chr21   26718345    .   AT  T   943.26  […]
`

(I can't resolve the second right now).
Any hint is appreciated at this point. I'm writing to snpEff developer for the same reason...

Post edited by Geraldine_VdAuwera on
Tagged:

Hi there,

The first set of alleles does not reduce to AT/T. It's actually a much more complex substitution (you'll see if you look closely). The Haplotype Caller is doing the right thing here and this error lies solely in the snpEff code, so unfortunately there's nothing we can do to help you here.

Eric Banks, PhD -- Director, Data Sciences and Data Engineering, Broad Institute of Harvard and MIT

Hi there,

The first set of alleles does not reduce to AT/T. It's actually a much more complex substitution (you'll see if you look closely). The Haplotype Caller is doing the right thing here and this error lies solely in the snpEff code, so unfortunately there's nothing we can do to help you here.

Eric Banks, PhD -- Director, Data Sciences and Data Engineering, Broad Institute of Harvard and MIT

• Member Posts: 31

Thanks. I had the answer from the developer, he confirmed that SnpEff cannot handle mixed events.
Well, at least you know that snpEff cannot handle (right now) those events, you may want to add some warning in the pages in which you suggest to use snpEff to predict variant effect.
d