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.

# --defaultBaseQualities in Haplotype caller

Member Posts: 6

Dear Team,
I'm getting the following error in Haplotype Caller (2.8-1):

argument --defaultBaseQualities has value -1.00, but minimum allowed value is 0.0

while according to the CommandLine documentation the default value should be -1.
I'm running GATK through Galaxy, where all the inherited arguments (including --defaultBaseQualities) and their default values are common to all the tools, and I only received this error with HaplotypeCaller.

Regards,
Paolo Uva

Tagged:

Ah, I did not know that about Galaxy, good to know. Not sure about the HC's handling of DBQs but basically if you have bases without qualities you'd probably want to throw them out anyway, so 0 should do just fine.

I will definitely fix the checking system so this no longer happens. I can't promise to get it done for 3.0 because I'm overcommitted right now, but I'll do it asap.

Geraldine Van der Auwera, PhD

Hi Paolo,

I'm sorry, that's a bug due to a new feature we put in to safety-check that the values of arguments are in range. I forgot to add an escape clause for out-of-range values that disable certain behaviors. I believe this should only happen if you are setting the argument to -1 at the command line rather than letting the default value be set internally. Can you check the command line that is generated to see if the one for HC explicitly sets this value to -1?

Geraldine Van der Auwera, PhD

• Member Posts: 6

Hi Geraldine,

you are right! The command line generated by the Galaxy wrapper for HC explicitly sets the value to -1. This happens because when selecting the advanced options of the GATK tools in Galaxy, all the parameters are sent to the command line explicitly with their default values.

As I cannot leave this parameter empty in Galaxy, at the moment I manually set --defaultBaseQualities to 0 (assuming this is equivalent to the default value internally set by HC).
However, it would be nice for the future release to let HC accept the same default values used by the other GATK tools.

Paolo