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

highly contaminated bins should get a warning not to use filtered data even after cleaning #29

Open
jvollme opened this issue May 27, 2022 · 1 comment
Assignees
Labels
documentation Improvements or additions to documentation enhancement New feature or request

Comments

@jvollme
Copy link
Collaborator

jvollme commented May 27, 2022

mdmcleaner is NOT designed to rescue terrible bins. It is only meant to validate good quality and to make good bins better!
This needs to be reflected in the results, so people are not encouraged to publish terrible bins (e.g. >20% contamination) after filtering

@jvollme jvollme added documentation Improvements or additions to documentation enhancement New feature or request labels May 27, 2022
@jvollme jvollme added this to the Improvements A milestone May 27, 2022
@jvollme jvollme self-assigned this May 27, 2022
@jvollme
Copy link
Collaborator Author

jvollme commented Sep 5, 2022

also check the pairwise identities of multi copy rRNA genes. Raise a warning if rRNA gene copies are less than 99% identical, regardless of final classification.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant