-
Notifications
You must be signed in to change notification settings - Fork 95
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
Can Sniffles2 detect SV variants which have no spanning reads covering the whole variant? #459
Comments
So Sniffles is not a tandem repeat caller. What I woudl expect is that you might be able to call these with lowering the mapping quality. Furthermore, the mimimum size of SV to be reported is set to 50bp! I dont know if this deletion that you show here is longer than 50bp.. |
@fritzsedlazeck |
I see. Maybe try by lowering the mapping quality.. but it also depends on the read length here. |
@fritzsedlazeck |
Did you had any luck? |
@fritzsedlazeck I tried with Sniffles with |
Yeah if its a BND that means part of reads map to a different location.. Maybe your expansion is too large... mmh. Have you considered a tandem repeat caller? Coming back to this after a while, I dont know if this is ONT or Pacbio data...? Dependent on this you could try Medaka /STRGLR (ONT) or TRGT (Pacbio). |
@fritzsedlazeck Yes, I tried tandem repeat caller. It is ONT, I tried strglr, and it yielded nothing. Indeed, you are right, the variant is very long. I tried different variant callers as a last resort, to see whether I might be able to detect it in some way after strglr came up with blank. |
One thing I had some luck with was medaka model. We just got this paper accepted: https://www.biorxiv.org/content/10.1101/2023.10.29.564632v1. |
@fritzsedlazeck Thank you. I am afraid they are also not doing too well with very long variants. |
mmh what if you assemble it ? e..g Flye ? |
I am failing to detect a long tandem expansion expansion in STR region.
All other tandem repeat expansions are detected as expected but they are much shorter and covered by at least some spanning reads with anchors at both ends, while this one is too long and all reads end up as soft clipped, leaving target region completely uncovered.
I am using single sample calling mode, with
--minsupport 2
and--tandem-repeats
with appropriate bed file, and getting no relevant SV in the region. I have also tried to do that without tandem repeat option, and it did not change the output in this region. I have also tried--minsupport auto
and--mosaic
, and still got nothing.Is there a way to detect this variant with Sniffles2?
The text was updated successfully, but these errors were encountered: