-
Notifications
You must be signed in to change notification settings - Fork 7
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
Paired-end Reads #6
Comments
Sorry for the tardy reply.
Yes, it should handle a single interleaved file of paired reads without problem and will remove both pairs if one is found to be human.
No. |
@bioinfoMMS Have you encountered any problems? Just checking. |
@multikengineer Thanks for the response and check in! No problems so far, the tool seems to be working just fine on the interleaved Fq file. |
Thank you @bioinfoMMS , and again apologies for my previous tardy response. |
According to #23 it seems it doesn't remove both pairs? |
Hi, #23 was written by a colleague, this issue was indeed present in version 2.0.0 . |
I might suggest using |
How does the scrubber tool handle paired-end reads? It looks like it takes only a single fastq file as input. If it is given an interleaved fastq file containing forward and reverse reads, does it use the paired information when classifying the reads as human? Or is it better to stitch the reads together with a certain number of 'N's' before giving it to the scrubber tool?
Thanks in advance!
The text was updated successfully, but these errors were encountered: