Low number of both surviving reads after trimming
Hi,
Trimming using Trimmomatic gave me these results:
code
trimmomatic PE -phred33 R1.fastq.gz R2.fastq.gz R1.paired.fastq.gz R1.unpaired.fastq.gz R2.paired.fastq.gz R2.unpaired.fastq.gz ILLUMINACLIP:adapter.fa:2:30:10 LEADING:20 TRAILING:20 SLIDINGWINDOW:4:15 MINLEN:25
output
Input Read Pairs: 429726444 Both Surviving: 160577915 (37.37%) Forward
Only Surviving: 268947096 (62.59%) Reverse Only Surviving: 91710 (0.02%) Dropped: 109723 (0.03%)
There was low percentage of both surviving reads, so, ?I performed trimming on R1 and R2.fastq separately, and the percentage of surviving reads in R1 and R2 each was over 99.9%. How can I interpret this trimming result?
Additionally, despite a both surviving rate is approximately 38%, the actual number of surviving leads is approximately 160M. I guess this is enough to continue with other processes, am i right?
Thanks!
0 answers
No answers yet.
Log in to answer this question.
More posts like this
-
Too many unpaired forward reads found by Trimmomatic
written by SilhouetteQ •
-
featureCounts percentage of successful assigned alignments lower than expected
written by gt •
-
fastq.gz unexpected end of file: Can this be fixed?
written by rebeliscu •
-
Trimmomatic couldn't generate output file
written by leukippus0116 •
-
Trimmomatic trims most of the reverse strand
written by hkarakurt
-
Bacterium genome hybrid assembly issue.
written by lynnchen31 •
-
Randomly got the following error: CRITICAL: Error executing: kneaddata_bowtie2_discordant_pairs but…
written by O.rka
-
Difference in number of reads in tophat and htseq-count outputs
written by nalandaatmi •
-
Trimmomatic low PE returns
written by oliver.tills •
Please edit your post and add the code parts again, this time use the
101010code button and NOT the double quote button. The latter is used to cite a source verbatim and mangles monospaced code formatting.Thanks, I modified.
I see that the code content was not added again, just the formatting modified. The output is still mangled. Compare it to the output you see on your screen and you'll notice that the post does not represent what you actually see.
Do you have a plot of adapter contamination for this data from FastQC? If you have a lot of adapter dimers, short inserts i.e. bad quality library then this would be an expected result.
Here is my fastqc, especially adapter content graph, before trimming(R1 and R2):
And this after trimming:
A significant fraction of your reads appear to have the nextera sequence, that combined to this directive
LEADING:20(do you have a reason to do this) are likely leading to very short reads which are likely being dropped once then hitminlen:25.If you are willing to try
bbduk.shfrom BBTools suite. A guide is available here: https://jgi.doe.gov/data-and-tools/software-tools/bbtools/bb-tools-user-guide/bbduk-guide/Thank you for your response.
There was no particular reason of
LEADING:20 and TRAILING:20, but I used the same parameters as I had used in previous projects which preferred to maintain high quality reads.In fact, this data has many 'total sequences' because replicates are concatenated, so I wanted to extract highly reliable sequences and do downstream analysis. Therefore, even if both survival rates are approximately 38%, the actual number of surviving leads is approximately 160 million. What do you think about using the results after trimming to continue the rest of the process?
It is your data and if you want to do that it is up to you. You may be throwing away essentially good data (you should remove the nextera sequences for sure). My guess if
LEADING:20may be coming from a particular pattern one sees in tagmentation/random priming-based sequence datasets.Read more about that here (if you did not know): https://sequencing.qcfail.com/articles/positional-sequence-bias-in-random-primed-libraries/
Thank you for your opinion.
I will try with lower LEADING and TRAILING bases. By the way, I tried to set
keepBothReads:truethrough search and got the following result:There are explanations for those parameters, but I still don't understand them clearly. ?Could you please explain a little more?