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
The nextstrain app route to dataset pipeline will look like this:
nextstrain.org/:virus/:strain/:timeperiod, thus: nextstrain.org/flu/h3n2/3y
nextstrain.org/:virus/:strain/:timeperiod
nextstrain.org/flu/h3n2/3y
How we map this to a REST route on the server, and then to string names on s3 is an open question
The text was updated successfully, but these errors were encountered:
Good question. The current practice for S3 is:
/data/h3n2_3y_tree.json /data/h3n2_3y_sequences.json /data/zika_tree.json
The issue is, some viruses (like Ebola and Zika) have only one resolution (timeperiod) and only one lineage (strain).
What about just doing the exact same structure for S3? So
/data/flu/h3n2/3y/tree.json /data/flu/h3n2/3y/sequences.json /data/zika/tree.json
Sorry, something went wrong.
That's ideal, if it's not too inconvienient, as we can construct the request on the client
Seems entirely reasonable. Shouldn't be an issue with the builds.
trvrb
rneher
No branches or pull requests
The nextstrain app route to dataset pipeline will look like this:
nextstrain.org/:virus/:strain/:timeperiod
, thus:nextstrain.org/flu/h3n2/3y
How we map this to a REST route on the server, and then to string names on s3 is an open question
The text was updated successfully, but these errors were encountered: