Notice:
If you happen to see a question you know the answer to, please do chime in and help your fellow community members. We encourage our fourm members to be more involved, jump in and help out your fellow researchers with their questions. GATK forum is a community forum and helping each other with using GATK tools and research is the cornerstone of our success as a genomics research community.We appreciate your help!

Test-drive the GATK tools and Best Practices pipelines on Terra


Check out this blog post to learn how you can get started with GATK and try out the pipelines in preconfigured workspaces (with a user-friendly interface!) without having to install anything.

Gatk Variantannotator not reannotating old rsIDs

Hello Everyone,

I am trying to reannotate some .vcf produced using the miSeq pipeline using dbSNP version 137.

I am currently using VariantAnnotator to reannotate the called variants with the latest dbSNP version in order to ropvide the latest information on the called variants. I am currently using the following command:
PATH/TO/GATK -T VariantAnnotator -R path/to/hg19.fa --dbsnp dbSNP_147_hg19.vcf --variant starting.vcf -o final.vcf

As far as I understood, VariantAnnotator should remap the alleles and match them with the latest dbSNP, also removing rsIDs that were remapped to other locations compared to the dbSNP I'm using as reference. However, when I look at the final vcf, some rsIDs that were incorrectly reported during the miSeq Variant Calling are still there and often maps to different position compares to the ones stored in the latest dbSNP release.

A couple of examples:

  • In both my starting and final vcf rs41309540 is reported. It is found mapping on chrX:123042989 and represent the G/C allele. However, on the dbSNP official webiste, is reported at chrX:123909139 and represents the A/G switch. (source: http://www.ncbi.nlm.nih.gov/projects/SNP/snp_ref.cgi?rs=41309540)

  • rs71646826 is reported by the miSeq pipeline to represent an A/C snp in chr1:240371085. However, when queried on the last dbSNP version, not only the alleles are different (A/T) but also its coordinates are different (chr1:240207785).

    Am I using VariantAnnotator properly? If so, what is going on exactly? Should I remap the rsIDs using another tool instead?

Thanks a lot for your help!

Cheers,

Daniele

Best Answer

Answers

Sign In or Register to comment.