Entering edit mode
6.3 years ago
Lucila
▴
20
Hi all, after running Trimmomatic (Illumina, 150bp paired end reads), I found that I have a lot more forward only surviving reads than reverse only surviving reads (7-8% vs. 0.5% approximately) for all my samples. Is this normal? Any ideas about why does it happen?
Thank you in advance for your help, Lucila.
What is the command you are using? Did you check the quality of the reads before trimming? It is not uncommon for reverse reads to have slight lower quality than forward reads, so quality trimming would affect R2 more.
Thank you for your answer. Here is an example of the command that I used:
I have checked the quality of all my samples before trimming and the parameters Per base sequence quality and Per sequence quality scores were OK for all the samples. I obtained FAIL in the following parameters: Per base sequence content, Per base GC content, and Sequence Duplication Levels.
FAIL
needs to be taken with a big pinch salt (I assume you are referring to FastQC results). You should read informative blog posts by group that wrote FastQC here. Most probably there is no problem with your sequence data. There is likely no need to do TRAILING/LEADING trimming either.Thank you so much genomax! Very useful link.
See this previouis discussion about Trimmomatic. A: Interpretation of Trimmomatic Results after Paired-End Adapter Trimming
By default, trimmomatic deletes the reverse read when it trims adapters from paired reads, leaving an excess of unpaired forward reads.
Just to be sure, you did trim them together correct?
I put both libraries in the same command, I have copied an example of the command I have used in the previous answer.
(deleted by the author)
I am having the same issue. But when I align to the genome using bowtie2, I get an error:
Error, fewer reads in file specified with -2 than in file specified with -1 terminate called after throwing an instance of 'int' (ERR): bowtie2-align died with signal 6 (ABRT)
You can try
repair.sh
from BBMap suite to re-sync paired end reads in the two files and remove singletons. This happens when you scan/trim paired end reads independently.