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

Investigate and improve the pipeline's read-merging behavior #87

Open
harmonbhasin opened this issue Nov 13, 2024 · 1 comment
Open
Assignees
Labels
bug Something isn't working priority_2

Comments

@harmonbhasin
Copy link
Collaborator

Jeff did some digging around and found some weird behavior between bbmerge and bowtie2 where paired reads that we'd expect to be merged aren't always merged and vice versa. It would be good to know how often this happens, and see if we can prevent this behavior from happening by changing parameters in one or both of the softwares.

@harmonbhasin harmonbhasin added bug Something isn't working priority_1 labels Nov 13, 2024
@harmonbhasin harmonbhasin self-assigned this Nov 13, 2024
@willbradshaw willbradshaw changed the title Investigate weird behavior between bbmerge and bowtie2 Investigate and improve the pipeline's read-merging behavior Dec 17, 2024
@willbradshaw
Copy link
Contributor

Further investigation suggests that we do have a genuine issue here, where about 5-10% of reads are being incorrectly merged by BBMerge in a way that other approaches to merging can handle better. While this isn't a terrible failure rate, we should still investigate and see if we can improve the situation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working priority_2
Projects
None yet
Development

No branches or pull requests

2 participants