Closed gringer closed 7 years ago
Hi David!
Thanks for the report! This bug has the same base as the Issue #60 which I just closed. Try doing a pull, make modules and make. The problem was a bug introduced in the last release which caused a faulty check of reference bounds. In your case, that happened for reverse complemented sequences only. I did a synthetic check for your situation locally and managed to reproduce it, and in the version 0.5.2 it is now fixed.
Thanks again!
Best regards, Ivan.
I'm a little confused as to what's going on here. I'm trying to map contigs from a different assembly (generated from the same input nanopore reads) to the 33 longest contigs in an assembly, and getting mappings that extend past the end of the contig. Here are a couple of demonstrative images, first the assembly mapped to itself:
t3_contigs_2017-May-17.pdf
And next an assembly with slightly different assembly parameters mapped to the same contigs:
t3_2_contigs_2017-May-17.pdf
The text on each line appears at the end of the contig, so there are at least 6 mappings that extend past the end. I thought something along the lines of "okay, so it's got a good mapping to the start, and just extends the read as far as it can". But then I looked at the mpileup results:
Those Ns are where the contig finishes. The odd thing is that there are INDELs defined past the end of the contig, which makes no sense to me.