Notice:
If you happen to see a question you know the answer to, please do chime in and help your fellow community members. We encourage our fourm members to be more involved, jump in and help out your fellow researchers with their questions. GATK forum is a community forum and helping each other with using GATK tools and research is the cornerstone of our success as a genomics research community.We appreciate your help!

Test-drive the GATK tools and Best Practices pipelines on Terra


Check out this blog post to learn how you can get started with GATK and try out the pipelines in preconfigured workspaces (with a user-friendly interface!) without having to install anything.
Attention:
We will be out of the office on November 11th and 13th 2019, due to the U.S. holiday(Veteran's day) and due to a team event(Nov 13th). We will return to monitoring the GATK forum on November 12th and 14th respectively. Thank you for your patience.

CombineVariants 'set' value separator is dash but can it be changed

I have a request for CombineVariants: can the separator between values in the "set=" keyword that is added to the INFO column be settable to something other than "-" (which I use in my sample names)? Comma would be nice. In fact, I think the VCF spec suggests it should be comma:

"INFO fields are encoded as a semicolon-separated series of short keys with optional values in the format: =[,data]."

You have the ##INFO line with Number=1, but it could be Number=., then use commas to separate each value in the INFO field.

Thanks.

Issue · Github
by Sheila

Issue Number
2069
State
open
Last Updated
Assignee
Array
Milestone
Array

Comments

  • SheilaSheila Broad InstituteMember, Broadie admin

    @tedtoal
    Hi,

    This will not be done in GATK3, but I will see what the developers say for GATK4.

    -Sheila

  • Geraldine_VdAuweraGeraldine_VdAuwera Cambridge, MAMember, Administrator, Broadie admin

    Hi @tedtoal, that's an interesting suggestion. We haven't yet ported CombineVariants to GATK4 (which has a completely new engine), and it's possible that we may not do a direct port, but instead reimplement some of its functionalities. The set annotation might become something you can annotate from VariantAnnotator (or equivalent). I agree that for parsing purposes it would be more convenient to use a comma-separated list instead of a single string with dashes. I'll put that in a ticket. That being said it will probably be a while before we get to this tool/port...

Sign In or Register to comment.