Skip to content
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

Annnotated VCF missing new INFO headers #11

Closed
sxv opened this issue Apr 27, 2016 · 4 comments
Closed

Annnotated VCF missing new INFO headers #11

sxv opened this issue Apr 27, 2016 · 4 comments

Comments

@sxv
Copy link

sxv commented Apr 27, 2016

When annotating with table_annovar.pl, my output VCF file contains several new entries in the INFO column, as expected. However these new INFO values are not added to the meta-information header lines at the top of the VCF file.

The VCF specification states "It is strongly encouraged that information lines describing the INFO, FILTER, and FORMAT entries used in the body of the VCF file be included in the meta-information section."

Several downstream VCF tools, including bcftools, require these INFO headers to be present in order to parse VCFs. So while they are technically optional, it seems like best practice to include them in the VCF output.

Thoughts?

@kaichop
Copy link
Contributor

kaichop commented Apr 27, 2016

They should be included.
If you can provide the command line and the example header that would be
helpful.

On Tue, Apr 26, 2016 at 9:53 PM, sujay notifications@github.com wrote:

When annotating with table_annovar.pl, my output VCF file contains
several new entries in the INFO column, as expected. However these new INFO
values are not added to the meta-information header lines at the top of the
VCF file.

The VCF specification states "It is strongly encouraged that information
lines describing the INFO, FILTER, and FORMAT entries used in the body of
the VCF file be included in the meta-information section."

Several downstream VCF tools, including bcftools, require these INFO
headers to be present in order to parse VCFs. So while they are technically
optional, it seems like best practice to include them in the VCF output.

Thoughts?


You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
#11

@sxv
Copy link
Author

sxv commented Apr 27, 2016

Is it possible this was fixed in a recent release? I am unable to reproduce this result with the new version of ANNOVAR, but my old annotated VCFs lack the INFO headers..

@kaichop
Copy link
Contributor

kaichop commented Apr 27, 2016

Yes it is fixed in a previous release (not so recent though).

On Tue, Apr 26, 2016 at 10:18 PM, sujay notifications@github.com wrote:

Is it possible this was fixed in a recent release? I am unable to
reproduce this result with the new version of ANNOVAR, but my old annotated
VCFs lack the INFO headers..


You are receiving this because you commented.
Reply to this email directly or view it on GitHub
#11 (comment)

@sxv
Copy link
Author

sxv commented Apr 27, 2016

Great, thanks for your lightning speed response!

@sxv sxv closed this as completed Apr 27, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants