We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
--output-sequences
initially reported in #810 (comment)
When there are duplicate sequence records in the input --sequences, they are propagated to --output-sequences without any warning or error.
--sequences
augur filter should exit with an error.
augur filter
cat >metadata.tsv <<~~ strain col1 SEQ1 A SEQ2 B ~~ cat >sequences.fasta <<~~ >SEQ1 AAAA >SEQ2 GGGG >SEQ2 CCCC ~~ augur filter \ --metadata metadata.tsv \ --sequences sequences.fasta \ --output-metadata output-metadata.tsv \ --output-sequences output-sequences.fasta cat output-sequences.fasta # >SEQ1 # AAAA # >SEQ2 # GGGG # >SEQ2 # CCCC
Check for duplicates and throw an error similar to
augur/augur/filter/_run.py
Line 187 in da1c89d
The text was updated successfully, but these errors were encountered:
Successfully merging a pull request may close this issue.
initially reported in #810 (comment)
Current Behavior
When there are duplicate sequence records in the input
--sequences
, they are propagated to--output-sequences
without any warning or error.Expected behavior
augur filter
should exit with an error.How to reproduce
Possible solution
Check for duplicates and throw an error similar to
augur/augur/filter/_run.py
Line 187 in da1c89d
Your environment: if running Nextstrain locally
The text was updated successfully, but these errors were encountered: