Open brisk022 opened 7 years ago
As far as I can tell, the problem is with Bowtie >= v1.2.0. It seems to behave differently from <= v1.1.2. The same dataset does not generate any errors when processed with RSEM v1.3.0/Bowtie v1.1.2 but fails with the latest RSEM v1.3.0/Bowtie v1.2.1.1. At first, I thought it was the switch to TBB but I get an error whether Bowtie v1.2 was compiled with TBB or not.
Perhaps, you should add convert-sam-for-rsem step to rsem-calculate-expression by default or check for bowtie version and run it for bowtie >= v1.2.
I also noticed this and reported it to the Bowtie maintainers BenLangmead/bowtie#52
When using RSEM v1.3.0 with Bowtie v1.2.0, it reported the following error:
The temporary bam file has the reads in the following order:
The mates are not adjacent in the files produced by RSEM/Bowtie. Adding
--sort-bam-by-read-name
does not help. Below is the command.