You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
while working on issue #504, I've noticed that --db - (reading --db data from stdin) does not work and yields a Fatal error. This could be intended, for instance to avoid reading both queries and references from stdin. If not, allowing --db - would make the user interface more predictable and flexible.
## reading from process substitutions works
vsearch \
--uchime_ref <(printf ">query\nAAGG\n") \
--db <(printf ">parentA\nAAAA\n>parentB\nGGGG\n") \
--quiet \
--uchimeout /dev/null
## reading from stdin works for the queriesprintf">query\nAAGG\n"| \
vsearch \
--uchime_ref - \
--db <(printf ">parentA\nAAAA\n>parentB\nGGGG\n") \
--quiet \
--uchimeout /dev/null
## reading from stdin does not work for the referencesprintf">parentA\nAAAA\n>parentB\nGGGG\n"| \
vsearch \
--uchime_ref <(printf ">query\nAAGG\n") \
--db - \
--quiet \
--uchimeout /dev/null # Fatal error: Unable to get status for input file (-)
The text was updated successfully, but these errors were encountered:
I think --db generally does not accept - as argument meaning read from stdin. I think this was done intentionally to avoid the use of - for multiple arguments, which would cause problems.
VSEARCH could be rewritten to accept - for many/all input file options, but only allowing it used in one at a time.
while working on issue #504, I've noticed that
--db -
(reading--db
data fromstdin
) does not work and yields aFatal error
. This could be intended, for instance to avoid reading both queries and references fromstdin
. If not, allowing--db -
would make the user interface more predictable and flexible.The text was updated successfully, but these errors were encountered: