Tagged with #clipping
0 documentation articles | 0 announcements | 2 forum discussions

No articles to display.

No articles to display.

Created 2013-08-16 13:32:43 | Updated | Tags: unifiedgenotyper clipping indel-call

Comments (1)

GATK 1.6 claims to apply a fixed Q20 threshold to clip ends of the reads for the indel caller:

3. Indel Calling with the Unified Genotyper

[...] while many of the parameters are common between indel and SNP calling, some parameters have different meaning or operate differently. For example, --min_base_quality_score has a fixed, well defined operation for SNPs (bases at a particular location with base quality lower than this threshold are ignored). However, indel calling is by definition delocalized and haplotype-based, so this parameter does not make sense. Instead, the indel caller will clip both ends of the reads if their quality is below a certain threshold (Q20), up to the point where there is a base in the read exceeding this threshold.

Also here:

--min_base_quality_score / -mbq ( int with default value 17 )

Minimum base quality required to consider a base for calling. The minimum confidence needed in a given base for it to be used in variant calling. Note that the base quality of a base is capped by the mapping quality so that bases on reads with low mapping quality may get filtered out depending on this value. Note too that this argument is ignored in indel calling. In indel calling, low-quality ends of reads are clipped off (with fixed threshold of Q20).

Can this "fixed threshold of Q20" be changed to another value when running the Unified Genotyper?

Created 2012-09-27 08:13:35 | Updated 2012-10-18 00:51:39 | Tags: unifiedgenotyper indels clipping

Comments (9)


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! at org.broadinstitute.sting.utils.clipping.ReadClipper.hardClipByReferenceCoordinates(ReadClipper.java:512) [...]

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