Closed rwdavies closed 6 years ago
Several hours of debugging later I found out it was a separate error in my code and not SeqLib related, but caused by an out of bounds vector assignment that only manifest itself later on. Sorry for the false bug report!
Hey,
I have high coverage long read WGS. I'm running code like the following, and getting an error like show below. The weird thing is that while I can reproducibly associate it with a specific read when I run my code per-chromosome, the code runs over the read in question when I run the program over a specific region. Any advice? This is using the most recent version of SeqLib (e0daf6010c4f006523e8e11e12c748c3dbcc7aa7)
Thanks, Robbie
code around here https://github.com/rwdavies/STITCH/blob/master/STITCH/src/bam_access.cpp#L178