![]() |
|
![]() |
||||
Thread | Thread Starter | Forum | Replies | Last Post |
Does anybody know how to convert dbsnp to .vcf (variant calling format)? | alexbmp | Bioinformatics | 13 | 04-05-2015 10:24 PM |
variant annotation | Balat | Bioinformatics | 3 | 03-05-2013 01:59 AM |
Suggest a dbSNP annotation and cSNP prediction tool | vishakha.more17 | Bioinformatics | 1 | 03-14-2011 09:42 AM |
EnsEMBL variant effect predictor standalone error | ketan_bnf | Bioinformatics | 0 | 02-16-2011 08:05 PM |
about dbsnp versions and the best way to filter your variant list with it... | Fabrice ODEFREY | Bioinformatics | 2 | 09-02-2010 06:18 PM |
![]() |
|
Thread Tools |
![]() |
#1 |
Member
Location: South Africa Join Date: Nov 2008
Posts: 23
|
![]()
Hi there,
I have had several queries from users checking my snp annotations (i use both ANNOVAR and SNPeff) and tell me that a large percentage of their candidate SNPs that are called as unknown snps are actually present in the dbsnp 135 database. I have checked both annotators and neither have updated past 132. I know its possible to include these databases manually but before I take the plunge I just wanted to hear opinions if this is actually so critical (and if there isnt good reason it is currently excluded), surely the newer versions of dbsnp still contain errors and are relatively unstable? Any opinions on this would be appreciated. Thanks! |
![]() |
![]() |
![]() |
Thread Tools | |
|
|