Make taxonomy more consistently used #374
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
More consistently differentiate between unrefined and refined taxonomy. * Taxometer requires an unrefined, and errors on a refined one * Recluster DBScan can take either, but will warn if passed a refined one, and not `--no_predictor`. If refinement is needed and the requisite comp and ab are not passed, error * TaxVamb can take either, but warns like DBScan. Does not do addtional check for comp and ab, since this is always required for TaxVamb.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
CC @Las02 - this PR, if it passes all tests, should address your issues with the taxonomy being inconsistent.
Still needs a documentation update.