-
Notifications
You must be signed in to change notification settings - Fork 125
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
fix vsearch cluster filtering #715
Conversation
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As I mentioned on Slack, I'm not competent here either. But by accident I saw a message that could be made clearer, so made a suggestion.
Co-authored-by: Daniel Lundin <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The changes look good to me
Thanks for the reviews! I am currently testing the test_full dataset with the change and hope it passes (with --vsearch_cluster and without the proposed fix it failed). edit: indeed, it works! |
Closes #696
I have not confirmed myself whether that change allows for more clusters to pass.
My python skills are horrible, so I need some serious opinion whether that seems fine. Tests pass and test files seem fine as well.
PR checklist
nf-core lint
).nextflow run . -profile test,docker --outdir <OUTDIR>
).nextflow run . -profile debug,test,docker --outdir <OUTDIR>
).docs/usage.md
is updated.docs/output.md
is updated.CHANGELOG.md
is updated.README.md
is updated (including new tool citations and authors/contributors).