Clarify how priorities affect subsampling #695
Merged
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.
Description of proposed changes
Moves the
--priority
argument into the appropriate argument group (it only works as a subsampling argument), correct the existing help text to show that the input should be tab-delimited, and expand the help text to clarify how subsampling uses the given priority scores.The output from
augur filter -h
for priorities now reads:Related issue(s)
Fixes #622
Testing
Tested by CI.