You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When working with the attached fastq files I found that more reads are filtered out when filtering the reverse reads (10_2.fastq.gz) than when filtering both the forward (10_2.fastq.gz) and reverse reads. (I get the same results when using fastqFilter and fastqPairedFilter)
As I understand each file is filtered independently and only the pairs where both reads pass the filters are yielded., so this result looks odd to me.
papok
changed the title
filterAndTrim yelds more valid reads when filtering paired forward and reverse reads than when filtering the reverse reads alone.
filterAndTrim yields more valid reads when filtering paired forward and reverse reads than when filtering the reverse reads alone.
Jan 6, 2025
@papok Thanks again for this report. I think we've fixed the issue in our latest commit. You were right about the problem in the code line you identified. And I think there was another problematic line:
10_1.fastq.gz
10_2.fastq.gz
When working with the attached fastq files I found that more reads are filtered out when filtering the reverse reads (10_2.fastq.gz) than when filtering both the forward (10_2.fastq.gz) and reverse reads. (I get the same results when using fastqFilter and fastqPairedFilter)
As I understand each file is filtered independently and only the pairs where both reads pass the filters are yielded., so this result looks odd to me.
I'm running dada2 v1.32.0
The script with the test parameters is:
Is there any obvious mistake I'm making?
Thanks for your time and dedication.
David.
The text was updated successfully, but these errors were encountered: