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
It seems that Auspice v2 dataset JSON have become a de-factor standard way to link to a set of samples, like in nextstrain's fetch URLs.
If I remember it correctly, that JSON can easily be traversed to get the full set of mutations for each sample. I would like to accept those URLs (either the part after nextstrain.org/fetch/ or the whole URL) as an alternative to local .fasta filenames.
Or I should accept both file formats (.fasta and Auspice v2 dataset JSON) as well as several access methods (local file name, remote URL or piped stream), in any possible combination. I might need something like a rewindable stream so that I can look at the first few bytes, decide what it is, and then parse it from the beginning.
The text was updated successfully, but these errors were encountered:
It seems that Auspice v2 dataset JSON have become a de-factor standard way to link to a set of samples, like in nextstrain's fetch URLs.
If I remember it correctly, that JSON can easily be traversed to get the full set of mutations for each sample. I would like to accept those URLs (either the part after
nextstrain.org/fetch/
or the whole URL) as an alternative to local.fasta
filenames.Or I should accept both file formats (
.fasta
and Auspice v2 dataset JSON) as well as several access methods (local file name, remote URL or piped stream), in any possible combination. I might need something like a rewindable stream so that I can look at the first few bytes, decide what it is, and then parse it from the beginning.The text was updated successfully, but these errors were encountered: