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!

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.

#### ☞ 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!

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.

GATK 3.7 is here! Be sure to read the Version Highlights and optionally the full Release Notes.

# UnifiedGenotyper glm mode INDEL error

Member Posts: 9
edited October 2012

Hi,

I'm running the UnifiedGenotyper (gatk version 2.0-35) with -glm INDEL on a dataset.
When I use -glm SNP everything works fine and I get my SNV calls, but if I use INDEL I get the following Error message:

org.broadinstitute.sting.utils.exceptions.ReviewedStingException: START (149) > (100) STOP -- this should never happen -- call Mauricio!
[...]

It looks like something is up with the read coordinates. I ran this particular script with -L 1 to limit to chromosome 1 but when I check the first and last reads of this chromosome everything seems to be in order (at least they map within the chromosome coordinates).

Cheers,
Paul

Post edited by Geraldine_VdAuwera on
Tagged:

I see -- just checking, and yes you're right that it's an optional step.

This looks like something that was recently fixed, could you try upgrading to the latest version of GATK, run the same command again and tell me if the problem persists?

Geraldine Van der Auwera, PhD

• Member Posts: 9

I just managed to narrow it down to one specific position in which it happens and it only happens if I have two input files file1.bam and file2.bam, for each file separately it runs fine.
Can't seem to find anything unusual about it thoug, the pileups look like this:

file1.bam

file2.bam

1 15436436 N 45 >><><>T>><>tTtTTTtTTTT+12TTGTGTGTTTGTt+12ttgtgtgtttgtT+12TTGTGTGTTTGTT+12TTGTGTGTTTGTT+12TTGTGTGTTTGTTt+12ttgtgtgtttgtt+12ttgtgtgtttgtt+12ttgtgtgtttgtt+12ttgtgtgtttgttTtTtttttttTT^It FHIIJHFJJDIGEJ@BADHCEHGHIGCJJJJJFJ<FDDDDDDDDD

Could it be the "-6nnnnnn" in file1.bam? I don't see anything unusual happen in the bam files otherwise, but I would guess it has something to do with one file having a variant and the process of determining the genotype of the other file at that locus.

Cheers,
Paul

Hi Paul, did you process your file with ReduceReads by any chance?

Geraldine Van der Auwera, PhD

• Member Posts: 9

Hi Geraldine, I did not do that.
I thought it was an optional step and so far I have no problems with storage so I decided to skip it.

I ran Picard's MarkDuplicates, extracted primary alignments vis 'samtools -F 256 [...]' (I then read that the UG filters for that anyway so it was probably unnecessary) and ran the IndelRealigner.
The resulting file is the input for my UG run.

Cheers,
Paul

I see -- just checking, and yes you're right that it's an optional step.

This looks like something that was recently fixed, could you try upgrading to the latest version of GATK, run the same command again and tell me if the problem persists?

Geraldine Van der Auwera, PhD

• Member Posts: 9

Thanks, that did the trick!
Cheers,
Paul

• Posts: 1

I just got the same error message with the 1.4-30-gf2ef8d1 version of GATK. It's a very cryptic message. What did you do to solve the problem? What causes this message?

Thanks,

Ilya

To solve the problem you need to update to the latest version of the GATK.

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

• Member Posts: 9

@ebanks said:
To solve the problem you need to update to the latest version of the GATK.

That is true for this specific instance but the error persists with other files I have even in GATK 2.1-12.
I haven't gotten around to checking in 2.1-13.

In my cases it's also usually specific to a single variant call, i.e. with the -L option ( and some sneaky use of nested intervals ) you can find the offending coordinate and then try to figure out what is going on or simply split your chromosome at that position and call everything before and after it.