In internal discussions on how to implement #860 and through my prototype in monkeypox/ingest, it seems like we've agreed to use the NDJSON format for streaming records between augur curate subcommands. However, users are unlikely to have their data in this format, so we would need to expand augur parse to support parsing to/from NDJSON format.
This idea was originally proposed by @trvrb in Slack.
Description
Add new subcommands to augur parse to handle:
FASTA -> NDJSON (with default output to stdout)
FASTA + TSV -> NDJSON (with default output to stdout)
NDJSON -> FASTA + TSV
We should probably keep augur parse backwards compatible as it is a widely used command (see search on cs.github.com)
Context
In internal discussions on how to implement #860 and through my prototype in monkeypox/ingest, it seems like we've agreed to use the NDJSON format for streaming records between
augur curate
subcommands. However, users are unlikely to have their data in this format, so we would need to expandaugur parse
to support parsing to/from NDJSON format.This idea was originally proposed by @trvrb in Slack.
Description
Add new subcommands to
augur parse
to handle:We should probably keep
augur parse
backwards compatible as it is a widely used command (see search on cs.github.com)