Greg found a bug in the way the junction script modifies the SAM file:
The latest version outputs a modified sam file, but there's a subtle case where it modifies one read but doesn't modify the paired end and they then become inconsistent. I looked at the code and there's no easy fix. So for now, I think we should just not output that modified sam file and have the pipeline just proceed with the original.
Greg found a bug in the way the junction script modifies the SAM file: