Closed vals closed 8 years ago
Nope --- no good reason. It's just that clipping support is a newer feature and it looks as if there was a bug. Thanks for the fix!
It turns out there were a few other corner cases that ticked off samtools --- these (at least the ones I was able to find) have been fixed as of e1cd39b804801ba6a6992ea0167fde28ff8fcbf5, and so samtools should happily process these files now.
Here is a segment of an output sam from RapMap:
If I try to use htslib (e.g. samtools) to parse this, I get errors due to
35M941S
not corresponding to 46 nts in the read.If I change
35M941S
to35M11S
the read parses fine. Is there a sensible reason for the S to be so long in the RapMap output?