Closed matthdsm closed 7 years ago
Also, the dbNSFP annotations aren't added to the variant_impacts table, but I suppose that's because they're not in a CSQ or EFF tag. @brentp, any idea if this could be solved?
Thanks Matthias
I saw this go by last week but forgot to have a look. I will look Tuesday morning. I suspect that you're right it's an issue with "-"
I just pushed a fix for this. It's not going to propagate to the variant_impacts table as that is for CSQ stuff as you noted. Please let me know if you see any more issues.
Hi Brent,
Thanks for the fix. Any chance in the future that these annotations will be included in the variant_impacts table? It would be nice to keep all functionality and not be dependent on VEP/snpEff.
M
Hi,
I'm running into an issue with dbNSFP annotations, but I'm not really sure if the issue is formed here, or in the geneimpacts module.
Our situation: Since VEP has proven to be untrustworthy with annotating dbNSFP, we've switched to vcfanno, which has been great so far. All required fields are available, with the right type.
VCF header:
However, in the case of the above M-CAP fields, the field name get parsed to
m_cap_pred, m_cap_rankscore and m_cap_score
, so everything gets lowercased and dashed are converted to underscores. That's good and all, minor issue, but the columns with the adjusted name contain no data al all.Is it possible that by changing the column name, the data lookup is broken?
example vcf entry:
Upon checking further, I notice all fields containing a dash (
-
) suffer from the same issue.Thanks for looking into this. M