snap
snap copied to clipboard
fixing off by one bug in BAM reader decodeSeqRC
If decodeSeqRC()
receives a read with an odd number of bases, the loop will write into position o_sequence[0]
instead of leaving it empty for the final if
to fill it in. This commit fixes the bug by adjusting o_sequence_pairs
to point one byte beyond the start of o_sequence
if the read length is odd numbered.
Can one of the admins verify this patch?