-
Notifications
You must be signed in to change notification settings - Fork 212
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ExAC DNPs #37
Comments
Sample VCF where 1000g, NHLBI EVS, and ExAC allele freqs are only provided for the SNPs, but not for the DNP: ##fileformat=VCFv4.2
##FORMAT=<ID=GT,Number=1,Type=String,Description="Genotype">
##FORMAT=<ID=AD,Number=G,Type=Integer,Description="Allelic Depths of REF and ALT(s) in the order listed">
##FORMAT=<ID=DP,Number=1,Type=Integer,Description="Read Depth">
#CHROM POS ID REF ALT QUAL FILTER INFO FORMAT TUMOR NORMAL
6 41903782 . A C . . . GT:AD:DP 0/1:10,10:20 0/0:22,0:22
6 41903783 . G A . . . GT:AD:DP 0/1:11,10:21 0/0:21,1:22
6 41903782 . AG CA . . . GT:AD:DP 0/1:10,10:20 0/0:21,0:21 |
I figure I could make this part of this gist for VEP installation, where I already require the user to edit the ExAC VCF with bcftools. Really, we just need a simple script that merges adjacent ExAC SNPs with similar allele-counts. The ExAC VCF is already sorted by position. So a one-liner is possible. |
I just figured out VEP's internal solution when reporting allele freqs from 1000g, ESP, or ExAC. They apparently report the freq of all non-reference alleles at the given |
Just hit a bottleneck. So as a workaround, I will report the sum of ACs of all non-reference alleles at a given position, even if it doesn't match the input allele. Same as explained in my last comment here. So for an input of |
This is now handled in 86e58e3 |
DNPs composed of two ExAC SNPs are not annotated.
Solution: add these DNPs (and TNPs?) to the vcf.
The text was updated successfully, but these errors were encountered: