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
{{ message }}
This repository has been archived by the owner on Jan 6, 2025. It is now read-only.
I have noticed that in both the example WGS dataset NA12878 and our own WGS data, Longranger does not detect any split/chimeric reads. In my experience, this has caused problems in SV detection on getting the exact break points right. It seems that split read information is supposed to be incorporated into SV calls, since there are fields in both Loupe and the large_sv_calls.bedpe file to report them.
Since Longranger/Lariat uses BWA for alignment, and BWA-MEM and BWA-SW are both capable aligning split reads, my question is, are the current parameters that are being used taking advantage of this function?
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I have noticed that in both the example WGS dataset NA12878 and our own WGS data, Longranger does not detect any split/chimeric reads. In my experience, this has caused problems in SV detection on getting the exact break points right. It seems that split read information is supposed to be incorporated into SV calls, since there are fields in both Loupe and the large_sv_calls.bedpe file to report them.
Since Longranger/Lariat uses BWA for alignment, and BWA-MEM and BWA-SW are both capable aligning split reads, my question is, are the current parameters that are being used taking advantage of this function?
The text was updated successfully, but these errors were encountered: