I'm running into a few cases where trimmomatic produces trimmed reads that are just a few bases long. Those can then map thousands or even tens of thousands times to contigs assembled by Trinity. In turn, that means that the bowtie2 quantification step is unable to complete in a reasonable amount of time since it is using -a. The solution is to add MINLEN:36 (I picked an arbitrary number) to the call to trimmomatic.
I'm running into a few cases where trimmomatic produces trimmed reads that are just a few bases long. Those can then map thousands or even tens of thousands times to contigs assembled by Trinity. In turn, that means that the bowtie2 quantification step is unable to complete in a reasonable amount of time since it is using
-a
. The solution is to addMINLEN:36
(I picked an arbitrary number) to the call to trimmomatic.