Skip to content
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

option to remove reads that fail the Casava filter #107

Closed
marcelm opened this issue Mar 14, 2015 · 4 comments
Closed

option to remove reads that fail the Casava filter #107

marcelm opened this issue Mar 14, 2015 · 4 comments
Labels

Comments

@marcelm
Copy link
Owner

marcelm commented Mar 14, 2015

From [email protected] on February 10, 2015 17:22:41

Hi,
I use cutadapt to trim Illumina reads for adaptor sequences and low-quality bases. I would love to also have the option to filter out reads that fail the Casava 1.8 filter ("Y" in sequence id line) since the fastq files I receive contain failed reads.
Thanks for considering this (easy) filter,
Jen

Original issue: http:https://code.google.com/p/cutadapt/issues/detail?id=97

@marcelm
Copy link
Owner Author

marcelm commented Mar 14, 2015

From [email protected] on February 11, 2015 05:17:20

Give me a few days to think about this. Sure, it’s easy to implement, but it does not have to do anything with adapter trimming per se. But then quality trimming, which cutadapt also does, is also not really adapter trimming ...

@marcelm
Copy link
Owner Author

marcelm commented Mar 14, 2015

From [email protected] on February 11, 2015 06:20:17

Thanks for considering. I like to use cutadapt as a high quality, tunable one-stop-shop for preprocessing, including adaptor trimming, quality trimming, length filtering (post-trim), and (ideally) Casava-filtering. Saves me time not to have to do each step separately, since I/O is the slow part!

@marcelm
Copy link
Owner Author

marcelm commented Mar 14, 2015

From [email protected] on February 11, 2015 06:54:32

I understand because that’s how I like to use cutadapt myself ;-). However, disk I/O shouldn’t be an issue even if you use multiple programs since you can use a pipe to connect them together, similar to this:

my-casava-filter-program input.fastq | cutadapt -a ADAPTER - > output.fastq

(Assuming here that my-casava-filter-program writes the reads to standard output.)

@marcelm
Copy link
Owner Author

marcelm commented Mar 14, 2015

From [email protected] on February 11, 2015 07:39:10

True! But there arent any (good) Casava-filtering programs out there (that
I could find). I wrote a quick awk script but Im not really a programmer.
Imight also have to pipe through gzip (twice) to handle the fastq file
de/compression.
Anyway, thanks for considering, its certainly true there are other options!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant