Details
-
Type:
Bug
-
Status: Closed (View Workflow)
-
Priority:
Major
-
Resolution: Fixed
-
Labels:None
Description
Open a BAM file; do not load sequence. Open sliced view. Zoom in until you can see the actual sequence on the reads. Double click/select a read that is in a relatively deep stack (>20 reads) but set the read depth to 10. There is a very good chance that the selected read does NOT appear in the sliced view because it gets incorporated into the summary/collapsed line of reads that the top of the frame. Also notice that the reads showing in the zoomed in main view are NOT the same set of reads being shown in the sliced view - all of this is due to read packing.
Sourceforge# 3046549
**editted to refine the problem (original issue was that the sequence of a selected read is not appearing in the sliced view.)
Attachments
Activity
I cannot reproduce this bug.
The link does not work, so I tried to test with other BAM files. When I set the horizontal zoom all the way to the right then load the BAM file, it is a blank screen. When I open sliced view, it is a blank screen.
Find a gene where there are about 20 reads deep, set max depth to 10. Select (highlight) a read in the visible stack. Zoom in to about 1 exon wide image. NOW open sliced view. Sliced view did/does repack just the visible reads, and this can cause the selected read to move 'up' into the summary reads, or just significantly move location within the stack of reads.
The fix would be to NOT permit sliced view to repack - repack should only happen in main view.
Passed Windows v12138
I cannot reproduce this bug.