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
Is there a way (or would be difficult) to output a BAM with the reads that contributed to the SV calls, with a SAM tag that identifies which call? This is super useful for debugging calls in IGV. For example, see the GATK HaplotypeCaller assembly BAM output.
The text was updated successfully, but these errors were encountered:
That would be useful, but I think the best place fo etc this output would be in SVTyper. We are better able to determine which reads support the SV in the genotyping stage. Check out the ‘-w’ flag in SVTyper.
On Jan 28, 2022, at 11:19 AM, Nils Homer ***@***.***> wrote:
Is there a way (or would be difficult) to output a BAM with the reads that contributed to the SV calls, with a SAM tag that identifies which call? This is super useful for debugging calls in IGV. For example, see the GATK HaplotypeCaller assembly BAM output.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
You are receiving this because you are subscribed to this thread.
Is there a way (or would be difficult) to output a BAM with the reads that contributed to the SV calls, with a SAM tag that identifies which call? This is super useful for debugging calls in IGV. For example, see the GATK HaplotypeCaller assembly BAM output.
The text was updated successfully, but these errors were encountered: