text: user2869: I received (from manufacturer) several .bam files and I used four callers (samtools, freebayes, haplotypecaller, deepvariant) to find some sequence variants. In obtained .vcf files, I took a closer look to some calls. I found interesting, homozygous one rs477033 (C/G Ref/Alt) with flag 'COMMON=0' and very low MAF. I also checked the .bam file (in IGV) and this rs itself in ensembl database. It looks like this:
  
  The problem is: in this case ref and alt are switched. The G is reference (ancestral) allele and C is altered. Nevertheless in the .bam file it's interpreted in opposite way. Of course it's false positive variant - there's no mutation there at all. All variant callers returned it as high quality variant. My. bam files are full of them.
  What went wrong in this case? Problem with mapping?
  How can I fix this thing, to get only novel and rare true positive variants?
  
  user77: The ancestral allele is not always the reference allele. Ref and alt aren't switched, ref is just rare in at least the population you're looking at (it appears to be rare in humans as a whole). So, the C is indeed reference and G is indeed altered, it's just that people homozygous for the G are the overwhelming majority. This is evidenced by the rs477033 variant being named NC_000001.11:g.165890393C>G. So, in short, nothing went wrong, all tools functioned correctly.
  You'll notice a bunch of these over time, either make a database of them (or find one, someone may have made one) and filter them out or see if maybe the 1000 genomes reference genome has some of these modified (or maybe the T2T genome that was recently published).
  
original_text: 2869: <p>I received (from manufacturer) several .bam files and I used four callers (samtools, freebayes, haplotypecaller, deepvariant) to find some sequence variants. In obtained .vcf files, I took a closer look to some calls. I found interesting, homozygous one rs477033 (C/G Ref/Alt) with flag 'COMMON=0' and very low MAF. I also checked the .bam file (in IGV) and this rs itself in <a href="https://www.ensembl.org/Homo_sapiens/Variation/Population?db=core;r=1:165889893-165890893;v=rs477033;vdb=variation;vf=248830" rel="nofollow noreferrer">ensembl</a> database. It looks like this:</p>
  <p><a href="https://i.stack.imgur.com/Iy364.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/Iy364.png" alt="igv" /></a></p>
  <p>The problem is: in this case ref and alt are switched. The G is reference (ancestral) allele and C is altered. Nevertheless in the .bam file it's interpreted in opposite way. Of course it's false positive variant - there's no mutation there at all. All variant callers returned it as high quality variant. My. bam files are full of them.</p>
  <p><strong>What went wrong in this case? Problem with mapping?</strong></p>
  <p><strong>How can I fix this thing, to get only novel and rare true positive variants?</strong></p>
   77: <p>The ancestral allele is not always the reference allele. Ref and alt aren't switched, ref is just rare in at least the population you're looking at (it appears to be rare in humans as a whole). So, the C is indeed reference and G is indeed altered, it's just that people homozygous for the G are the overwhelming majority. This is evidenced by the rs477033 variant being named NC_000001.11:g.165890393C&gt;G. So, in short, nothing went wrong, all tools functioned correctly.</p>
  <p>You'll notice a bunch of these over time, either make a database of them (or find one, someone may have made one) and filter them out or see if maybe the 1000 genomes reference genome has some of these modified (or maybe the T2T genome that was recently published).</p>
  