-
Notifications
You must be signed in to change notification settings - Fork 5
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
Parse ANN field #25
Comments
It doesn't look like tools are being helpful in standardizing the field representation The header line in the jannovar example is
Am I to assume that "Functional annotations: " is not just some freetext and is something I can programmatically parse? SnpEff proposes some standard layout of the ANN field but that might not be actually standard http://snpeff.sourceforge.net/VCFannotationformat_v1.0.pdf (haven't seen the header of the snpeff vcf but they might not include their version of it in the header info) |
I'm pretty sure Jannovar uses the same standard as SnpEff. I thought I saw that somewhere, but now I can't remember where. The history seems to imply they started using that in v0.12, though: https://doc-openbio.readthedocs.io/projects/jannovar/en/master/history.html |
There is also EFF but that is outdated "Note: Older SnpEff version used 'EFF' field (details about the 'EFF' field format can be found in the EFF Field section)." |
There is also CSQ from VEP https://useast.ensembl.org/info/docs/tools/vep/vep_formats.html this is sort of interesting from the GSoC projects on VEP |
probably code done on consuming app |
The ANN field is something with fields defined in the header and the field is | delimited https://github.com/GMOD/vcf-js/tree/add_ann_example
There is also SVANN I think
The text was updated successfully, but these errors were encountered: