Skip to content
New issue

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

Switching one component of the dataset doesn't preserve others #697

Open
tsibley opened this issue Jan 23, 2019 · 1 comment
Open

Switching one component of the dataset doesn't preserve others #697

tsibley opened this issue Jan 23, 2019 · 1 comment
Labels
bug Something isn't working please take this issue

Comments

@tsibley
Copy link
Member

tsibley commented Jan 23, 2019

For example, going to https://nextstrain.org/flu/seasonal/h3n2/ha/2y and then switching segment to na results in viewing https://nextstrain.org/flu/seasonal/h3n2/na/3y instead of na/2y. Similarly, switching lineage from h3n2 to h1n1pdm resets the selected segment and time resolution. It would be nice for dataset switches to preserve as much of the other selected components as possible (i.e. if they exist for the destination dataset).

@tsibley tsibley added the bug Something isn't working label Jan 23, 2019
@jameshadfield
Copy link
Member

Feel free to take this issue if anyone would like to tackle it. I believe that this functionality will be shifted to the client during the implementation of #687.

Some relevant info (using the above ha -> na example) - auspice only sends flu/seasonal/h3n2/na to the server. The server then completes this incomplete path using the default value (3y) as it doesn't know about the previous state.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working please take this issue
Projects
None yet
Development

No branches or pull requests

2 participants