Closed MatthewRalston closed 8 years ago
As explained in the README, I am not the official maintainer of Trimmomatic. For this issue, you should contact Anthony Bolger (http://www.usadellab.org/cms/index.php?page=trimmomatic). Note also that I made this repo with version 0.33 of the code, but I can see that it is now at version 0.36.
I developed a trivial test dataset to test the clipping capacity of trimmomatic with perfectly sequenced adapters (no mismatches). My read files are as follows:
fastq 1 (forward read)
fastq 2 (reverse read)
The behavior I am observing seems to be associated with the Simple clipping mode on paired-end data. Palindromic mode is not engaged in this circumstance. I was troubled to find that when contamination is in one read only, the whole read is dropped. This behavior is documented in the manual.
However, this is not desired behavior in nearly all circumstances. For example, consider the behavior of cutadapt, which clips the adapter-matching sequences when they are identified. In a very typical 2x100bp run, Trimmomatic will completely drop both reads if contamination is found at both the 5` and 3' end. It will also drop a read if the whole adapter sequence is found in it. This is clearly not "clipping" the adapters from the reads.
adapters.fa
test1.fastq
test2.fastq