-
Notifications
You must be signed in to change notification settings - Fork 129
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
potential output problem #126
Comments
The 23 reads are the (5022-4999) untrimmed ones. Since they are also written to an output file ( I agree this is confusing and should be changed, in particular because the reads in |
Actually, I still get the same 4630 number of reads, whether I use the --untrimmed-output (or the --too-short-output) option, or not. |
If you don’t use |
yes indeed ! Thank you for these explanations. |
I’ve opened issue #128 to track this. Thanks for reporting. |
Hi,
Using cutadapt like this (1.9dev1):
cutadapt -e 0.12 -m 25 --info-file="info.tab" --too-short-output="discarded_tooshort.fastq" --untrimmed-output="discarded_missing_adapter.fastq" -g $linker "trimmed_bc.fastq" -o "trimmed_linker.fastq" > "info.log"
gives me this output:
=== Summary ===
Total reads processed: 5,022
Reads with adapters: 4,999 (99.5%)
Reads that were too short: 392 (7.8%)
Reads written (passing filters): 4,630 (92.2%)
Total basepairs processed: 908,639 bp
Total written (filtered): 693,472 bp (76.3%)
However, when I count the number of reads in "trimmed_linker.fastq", I actually get 4,607 (4,999-392). What are these extra 23 reads counted in the 'Reads written (passing filters)' ?
The text was updated successfully, but these errors were encountered: