-
Notifications
You must be signed in to change notification settings - Fork 243
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
Genotype requires a method filtersWereApplied #741
Comments
+1, subscribing |
I guess the assertion was a way to say that you should always be able to do you think that there should also be a "wereFiltersApplied()" function On Mon, Nov 14, 2016 at 4:46 PM, Frank Austin Nothaft <
|
Yes, that would be my suggestion. Because of the special treatment |
This one has been sitting for a while, any update? |
I think that it's a reasonable idea. Genotype filters haven't loomed large in our world...(though this might soon change)...So I'm not sure that we would prioritize submitting the PR...but we will review it if you have a suggestion. |
Where do the assertions in #663 come from?
"A Genotype always has filters. If there are no non-PASS filters, it's PASS."
Per VCF specification:
"FT : sample genotype filter indicating if this genotype was “called” (similar in concept to the FILTER field). Again, use PASS to indicate that all filters have been passed, a semi-colon separated list of codes for filters that fail, or ‘.’ to indicate that filters have not been applied. These values should be described in the meta- information in the same way as FILTERs (String, no white-space or semi-colons permitted)"
Genotype
requires a methodboolean filtersWereApplied()
similar to that inVariantContext
to support this distinction.The text was updated successfully, but these errors were encountered: