Closed ghost closed 6 years ago
Thank you for this excellent report! @kghosesbg do you mind signing up to our mailing list if you have not done so? We will discuss sambamba development and priorities. This certainly belongs there!
For now, the easy fix is to use samtools. I'll add this to a milestone.
Hi,
I believe that this issue has been resolved in release v0.6.7. This issue stems from BAI pseudo-bin calculation in indexing.d from BioD. The BioD issue page that covered an incorrect pseudo-bin calculation in indexing.d doesn't appear to exist anymore, but you can see that the latest commit to this file applied the fix that I suggested for that issue. Release v0.6.7 of sambamba appears to have folded in this fix from BioD.
I have not encountered this issue when using sambamba v0.6.7 to index BAMs. You can confirm that this is the case in general.
Thanks @jfarek!
Problem:
NOCOOR
region.How to replicate:
g++ --std=c++14 read_nocoor.cpp -o rno /usr/local/lib/libhts.dylib /usr/lib/libz.dylib
(You may need to adjust for your local install)NOCOOR
python3 sambamba_bug.py
samtools index small_test.bam
sambamba index small_test.bam
Possibly important clue
If there are ONLY
NOCOOR
reads in the BAM file then this bug does not appear.tid=-1
or there is only one read savedCode
read_nocoor.cpp
sambamba_bug.py