Question: ./ Vs "0/0" In Vcf Files
gravatar for michealsmith
8.7 years ago by
michealsmith750 wrote:

I used GATK to call SNP/indel. And I called for five members of trio together. Result is like below:

G    A    89.43    PASS    AB=0.427;AC=2;AF=0.33;AN=6;BaseQRankSum=-1.468;DP=12;Dels=0.00;FS=0.000;HRun=1;HaplotypeScore=0.6373;MQ=60.00;MQ0=0;MQRankSum=0.536;QD=12.78;ReadPosRankSum=1.134;SB=-26.82;set=variant2    GT:AD:DP:GQ:PL    ./.    0/1:2,3:5:67.41:102,0,67    ./.    0/1:1,1:2:25.53:26,0,36    0/0:5,0:5:15.05:0,15,200

I'm just curious, what's the difference between "./." and "0/0" ? They both indicate there's no alternative allele, right? Then why use two different symbols? thx

vcf genotyping • 7.0k views
ADD COMMENTlink modified 6.6 years ago by stat.140520 • written 8.7 years ago by michealsmith750
gravatar for Aaronquinlan
8.7 years ago by
United States
Aaronquinlan11k wrote:

They are very different. 0/0 means that sufficient data was available in the alignments to conclude the absence of alternate alleles. That is, the alignments made it clear to the caller that only reference alleles were present. In contrast, ./. means that there was insufficient data to make any conclusions about that individual's genotype. This typically happens when there are very few (if any) reads aligned for that individual.

It may seem to be a trivial difference, but the absence of data is very different from the absence of alternate alleles. For example, if you wanted to compute the minor allele frequency for this variant, each allele in the 0/0 genotype should be added to the denominator, while the alleles from the missing (./.) genotypes should be omitted, as one is uncertain. Clearly, this changes the resulting frequency calculation.

This is addressed in the VCF spec: see the "Genotype fields" section.

ADD COMMENTlink modified 13 months ago by _r_am32k • written 8.7 years ago by Aaronquinlan11k

this is very helpful. thx. Then how to deal with these "./." ? Just disgard them? I'm doing trio analysis, to compare, say five family members within a trio..

ADD REPLYlink written 8.7 years ago by michealsmith750

They are just missing information, so you just need to handle that in a manner appropriate to the interpretation of your experiment. Sorry if that is vague, but I am not sure what else to say.

ADD REPLYlink written 8.7 years ago by Aaronquinlan11k

One option is to use one of the imputation pipelines to fill in the missing SNPs based on the local haplotype. Have a look at Beagle, impute2 and other similar pipelines. Beagle at least should be able to use the Trio/Pedigree structure which could help alot.

Also it won't work for filling in denovo variants but for your family it should do a pretty good job of filling in shared missing variants.

I would note though in the example your showing all the individuals have pretty low read depth coverage of that site. If you've only got half a dozen individuals and very low coverage even imputation will have issues if your missing too many vars.

ADD REPLYlink modified 8.7 years ago • written 8.7 years ago by eonsim100
gravatar for stat.1405
6.6 years ago by
stat.140520 wrote:

I faced like your problem and I found that every ./. corresponding to DP=0

so, it is because there is no read depth at this GT

ADD COMMENTlink written 6.6 years ago by stat.140520

In my VCF files, some genotypes are coded as 0/3 or 0/5 instead of 0/1.

What does it mean? does it mean something else other than just another heterozygote call?

ADD REPLYlink modified 14 months ago by _r_am32k • written 5.2 years ago by saurabhyadav150

What organism are you working with?

ADD REPLYlink written 4.4 years ago by akang90

This happens when there is more than one alternative allele.

Suppose your reference is A and the most common alt. allele is C, but G and T can also occur.


AC -> 0/1
AG -> 0/2
AT -> 0/3

I believe this is common in indels.

ADD REPLYlink modified 3.1 years ago • written 3.1 years ago by Leandro Lima960
Please log in to add an answer.


Use of this site constitutes acceptance of our User Agreement and Privacy Policy.
Powered by Biostar version 2.3.0
Traffic: 975 users visited in the last hour