Sunday, June 12, 2016

Those pesky bugs

I have found a bug in the code featured in the previous post where some of the reads hitting several anchors were mapped incorrectly. So to set the record straight, here are the updated mapping rates for the simple code that does not yet handle mismatches or indels:


Dataset% reads w/ a unique correct mapping% reads w/ at last one correct mapping
1Mln reads, 100bp91.07100.00
300K reads, 300bp93.32100.00
10K reads, 1000bp94.84100.00

I wish that all bugs were like this and automagically improved performance :) Well, onto the mismatches then...

No comments: