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.
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!

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.
Picard 2.9.0 is now available. Download and read release notes here.
GATK 3.7 is here! Be sure to read the Version Highlights and optionally the full Release Notes.

# Probable bug in SelectVariant --maxIndelSize

Member, Broadie Posts: 43 ✭✭

Dear All,

Just thought I should report a possible small bug with SelectVariant --maxIndelSize as I think it's only filtering insertions greater than the given value and not deletions.
Of course using JEXL expressions I can still get the variants I'm after...

Cheers,
Laurent

Tagged:

Hi Laurent,

Thanks for pointing this out, we'll take a look at what's going on there. Are you using the latest version (2.4-7)?

Geraldine Van der Auwera, PhD

• Member, Broadie Posts: 43 ✭✭

Hi Geraldine,

Yes, I am using 2.4-7. To be entirely fair, it could be debated whether this is the desired behavior (as deletions would be of negative length when compared to the reference genome) but maybe it could be specified in the documentation then. Also the fact that there is no --minIndelSize option got me thinking the the --maxIndelSize would perform size selection on both insertions and deletions.

Cheers,
Laurent