Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
CRAM layout can get messed up #1271
The layout of CRAM features can get messed up possibly near block boundaries?
To reproduce I uploaded a sample data directory. Start at the start of the chromosome and then scroll to the end of the data and the layout will be weird and mouseovers will not work at the end right where the features end
Tested on 1.15.3 and dev branch. The same thing does not appear to happen with BAM versions of the same file
Now, the interesting thing is i think it is due to ID collisions. If I make a simple hashmap collision detector e.g.
Then this outputs a lot of collisions in the areas that the layout is bad