You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
I'm not sure if this is intended behavior, but the --haploid flag appears to be significantly less sensitive at detecting variants than the default setting. Looking at the code in call_var.py it appears to be because of this snippet:
, seems to be returning that anytime there is a hetereozygous variant it defaults to reporting the reference variant when in --haploid mode.
My expectation was that --haploid mode would be more sensitive at detecting low frequency variants rather than defaulting to the reference more frequently. If this is intended behavior it may be worth clarifying what --haploid mode is doing behind the scenes and what assumptions it's making in the --help statement.
Thanks!
The text was updated successfully, but these errors were encountered:
Two new modes added. --haploid_precision will consider heterozygous alike positions as non-variant.--haploid_sensitive will consider heterozygous alike positions as variant.
Hello,
I'm not sure if this is intended behavior, but the
--haploid
flag appears to be significantly less sensitive at detecting variants than the default setting. Looking at the code in call_var.py it appears to be because of this snippet:Which based on the later return statement in that function,
, seems to be returning that anytime there is a hetereozygous variant it defaults to reporting the reference variant when in
--haploid
mode.My expectation was that
--haploid
mode would be more sensitive at detecting low frequency variants rather than defaulting to the reference more frequently. If this is intended behavior it may be worth clarifying what--haploid
mode is doing behind the scenes and what assumptions it's making in the--help
statement.Thanks!
The text was updated successfully, but these errors were encountered: