[ensembl-dev] Writing VCF header lines in plugins
Will McLaren
wm2 at ebi.ac.uk
Thu May 29 10:26:43 BST 2014
Hi Konrad,
Thanks for the suggestions; both good ideas, but I think they will have to
wait for the next VEP release.
Fortunately this will coincide with the first Ensembl release on GRCh38!
Regards
Will McLaren
Ensembl Variation
On 28 May 2014 22:37, Konrad Karczewski <konradk at broadinstitute.org> wrote:
> Hi everyone,
>
> I noticed we can use get_header_info to write into the VEP header, but
> when this writes to VCF, it simply puts the key into the pipe-delimited
> list. Is there any way a plugin can put more info into the VCF header?
> Particularly, I was wondering if it'd be possible to write a separate line
> with plugin (and VEP) version info.
>
> Actually, regardless and slightly related, VEP version info (and
> command-line parameters) would be a useful thing to write into the VCF, a
> la Picard/GATK. Would help in reproducibility (especially as GRCh38 comes
> along).
>
> -Konrad
>
>
> _______________________________________________
> Dev mailing list Dev at ensembl.org
> Posting guidelines and subscribe/unsubscribe info:
> http://lists.ensembl.org/mailman/listinfo/dev
> Ensembl Blog: http://www.ensembl.info/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.ensembl.org/pipermail/dev_ensembl.org/attachments/20140529/9323567a/attachment.html>
More information about the Dev
mailing list