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
The only problem with doing this is that we would no longer be able to write the evidence BAM on the fly - we'd have to write a temporary BAM with all reads supporting all break-points, and then re-process that to remove reads/templates for breakpoints with insufficient support. That's not a big overhead - these BAMs are usually pretty small. And it would also give us a logical place to add re-sorting the BAM file into coordinate order for use in IGV.
The text was updated successfully, but these errors were encountered:
Alternatively this could be a separate tool FilterPileup that takes in the raw pileup, filters the text file and then filters the BAM file emitted by SvPileup.
I'm envisioning we could add parameters like:
The only problem with doing this is that we would no longer be able to write the evidence BAM on the fly - we'd have to write a temporary BAM with all reads supporting all break-points, and then re-process that to remove reads/templates for breakpoints with insufficient support. That's not a big overhead - these BAMs are usually pretty small. And it would also give us a logical place to add re-sorting the BAM file into coordinate order for use in IGV.
The text was updated successfully, but these errors were encountered: