-
Notifications
You must be signed in to change notification settings - Fork 26
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
Tips of reads can overlap in X by fractions of a base #418
Comments
I looked at these more and the reads are indeed overlapping by exactly 1 SVG pixel unit. The X + width of the final rectangle in that blue read on the right is 1 more than the X of the first rectangle of that red read it bumps into. We probably need to look at the functions that compute read start and end X coordinates: sequenceTubeMap/src/util/tubemap.js Lines 2656 to 2680 in 56d3c4b
But I have no idea where we're getting the 1 pixel of overlap. |
To follow the view link, you should be able to start your local tube map and then click it. The node I am looking at is near the middle of the rendered visualization. |
Actually, the problem might be here: sequenceTubeMap/src/util/tubemap.js Lines 3787 to 3788 in 56d3c4b
We generate the rectangle list entries with exactly coinciding start and end coordinates, and then we add a +1 when we go to draw the SVG elements for them for some reason. |
In this view, reads crossing an expanded gap between nodes can get bumped down a lane because they overlap other reads in X by a few pixels, not an entire base. See this image:
Read lines should always start and end exactly on base boundaries. There shouldn't be apparently random slop of a few pixels here or there.
The text was updated successfully, but these errors were encountered: