-
Notifications
You must be signed in to change notification settings - Fork 311
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
Variant filter representation #194
Labels
Milestone
Comments
Neal, I presume you're still waiting for comments on this one? |
See also: |
Shall we close this? |
heuermh
added a commit
to heuermh/adam
that referenced
this issue
Jul 26, 2016
…ty filters, fixes bigdatagenomics#194 (cherry picked from commit 37e1673)
Fixed by #1250 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
VCF format specifies that the FILT column can take on the following values:
"PASS" - variant passed all filters
Comma-separated list of failing filters - filters that the variant call failed
"." - no filter applied
(see http://gatkforums.broadinstitute.org/discussion/3401/filter-column-in-vcf-file-from-haplotypecaller for a discussion on the output of the haplotype caller)
Right now, we have two fields in VariantCallingAnnotations:
This table indicates the value of each variable for the different scenarios:
@mlinderm brought up that there is some ambiguity - we don't know the difference between variant passing and no filters applied without checking another field (the list of filters applied), and also people doing analysis were only likely to check the boolean, since that's what is done with the VCF field. The proposal is to go back to the original way, which was:
union { null, boolean } variantIsFiltered = null; array<string> failingFilters = null;
New table:
Note that in the case where the variant passed, the passing filters should still be available from the VCF header.
Thoughts?
The text was updated successfully, but these errors were encountered: