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.

# Het calls from HaplotypeCaller with no ALT reads

Member Posts: 13
edited January 2014

Hi

With HaplotypeCaller,Version=2.8-1-g932cd3a

In the raw VCF we are seeing instances of

A HET call (0/1) but there are no ALT reads (22,0)

### Some Questions to clarify

a) Is this VCF format valid?

b) Is this intended or bug?

c) Are there current process that would filter these entries?

i) We've tried SelectVariants with --ExcludeNonVariants but the entries are still there

ii) Would downstream steps such as variant recalibration/filter catch these?
`

### More Technical details:

This was run using Queue,

I've attached the VCF, I'm assuming the Command line information in the VCF header is sufficient?

Regions of interest (I've been greping for ",0:" )

chr2 212543723

chr3 10088443

If this is a bug. Let me know if you would like me to provide some bams

Thanks

Post edited by kevyin on
Tagged:

Hi @kevyin,

Have you looked at the pileup of reads at those positions? It is possible that some reads supporting the allele are present but not counted in the genotype field due to filtering or soft-clipping. You should look at the site in IGV, with the option to show soft-clipped reads activated (this is very important).

If there is still no evidence for the calls then we would need a snippet of the bam file that reproduces the error, in order to debug this locally. But first we want to see a screenshot of the site showing that there is no supporting data.

Geraldine Van der Auwera, PhD