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

Paired-end Reads #6

Closed
bioinfoMMS opened this issue Jun 3, 2021 · 7 comments
Closed

Paired-end Reads #6

bioinfoMMS opened this issue Jun 3, 2021 · 7 comments

Comments

@bioinfoMMS
Copy link

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!

@multikengineer
Copy link
Collaborator

Sorry for the tardy reply.

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?

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.

is it better to stitch the reads together with a certain number of 'N's' before giving it to the scrubber tool?

No.

@multikengineer
Copy link
Collaborator

@bioinfoMMS Have you encountered any problems? Just checking.

@bioinfoMMS
Copy link
Author

@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.

@multikengineer
Copy link
Collaborator

Thank you @bioinfoMMS , and again apologies for my previous tardy response.

@mbhall88
Copy link

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.

According to #23 it seems it doesn't remove both pairs?

@mikelchtermans
Copy link

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.

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 .
A fix for this issue was to pipe the output to the tool fastqtk with the command 'fastqtk drop-se <in.fq> <out.fq>' which in turn contained a bug, for which i created a pull request just now: ndaniel/fastqtk#6 .
We have not tested 2.1.0 seeing as it was not marked as resolved.

@mbhall88
Copy link

mbhall88 commented Jul 4, 2023

I might suggest using seqfu to deinterleave the output then in that case https://telatin.github.io/seqfu2/tools/deinterleave.html

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

No branches or pull requests

4 participants