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!

Get notifications!


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


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.

Jump to another community
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.

HaplotypeCaller and Coverage. I get ./. but I have coverage

NadiaNadia Member Posts: 13

Hi, I'm calling Variants with HaplotypeCaller in a population of 2 Parents and 7 F1-individuals. After read backed phasing I'm combining the vcf files of my genotypes with CombineVariants. In the outfile I very often find "./.". I thought this means there is no coverage at a certain position. But at many positions I do have good coverage. Why do I then get ./.? Moreover I used FastaAlternateReferenceMaker and created a new reference sequence including the variants from the parents. In that case, after I run HC and do the phasing and combine variants steps, I only get "./." at positions where there is really no coverage (as I can see in my mappings).
Nadia

Best Answer

Answers

  • NadiaNadia Member Posts: 13

    oh yes of course! That makes sense! I will try both. Thanks a lot!

  • NadiaNadia Member Posts: 13

    when I run HC over all my sample together and then do Read-backed phasing, shall I merge all my mappings and do the phasing or rather not merge them? And if not, does it make a difference in which order I give them to the Read-backed phasing walker? Should it be the same order as the the order of the genotypes on the raw variants file (the HC output). In the past I have experienced that the phasing didn't work so well when I called all my samples together

  • pdexheimerpdexheimer Member, Dev Posts: 544 ✭✭✭✭

    I haven't done much with phasing, but IIRC it only works on trios - which would mean you'll have to run it once for each offspring. I think you'll then have to merge the resulting VCFs (does CombineVariants respect phase? I have no idea). Since you'd effectively be splitting the VCF by sample before phasing, the order that you run them shouldn't matter at all

Sign In or Register to comment.