Closed caioraposo closed 3 years ago
This is sort of a bizarre error - at least in the past, Trinity lumped all the reads together, anyway, so whether or not there were the same counts for R1 and R2 was a moot point. It seems that's not the case now - either as an update to Trinity or an update to fastool.
Regardless, one way to fix this is to stop using Trinity - it constantly changes in ways that break everything else.
Another fix to problem, if you still need to use trinity, that should work is simply to delete the singleton reads from any folder of trimmed fastq files you are trying to assemble. Then, they can't be lumped in with R1 reads (which is how your R1 counts differ from your R2 counts).
Removing the singleton reads did the trick, thank you.
Cool. Apologies for the issue - Trinity is a never-ending source of problems... Also, I'm going to re-open this to remind myself at some point to make this change. Thanks for reporting 👍.
Oh I'm sorry for that, the real issue wasn't resolved yet, we did only a work-around. But thanks again :)
After getting the error Neither Trinity.fasta nor trinity.log were found in output. The output provided by trinity.log was:
According to the log, the conversion from fastq to fasta didn't occur correctly because of the difference in the number of lines between the two files.
different from the output of phyluce_assembly_assemblo_trinity: