This is important so that data run with different settings can be sanely navigated without having to set up multiple deployments (e.g. dnaml vs parsimony tree building and ancestral reconstruction).
The challenge here will likely be in updating how we do routing and index our clusters. We'll also need some sort of option for "naming" a particular run so that there is a UI friendly way of selecting between different datasets. So maybe this is something we add as a scons param, with some default (uuid? scons command?).
My best guess of how things should work is there should be a dropdown on the top nav bar that lets you select the dataset, and the dataset identifier then becomes a base part of the route. And we could probably have our current CLUSTERS data maps (of cluster ids to cluster metadata) nest under maps with dataset keys.
This is important so that data run with different settings can be sanely navigated without having to set up multiple deployments (e.g. dnaml vs parsimony tree building and ancestral reconstruction).
The challenge here will likely be in updating how we do routing and index our clusters. We'll also need some sort of option for "naming" a particular run so that there is a UI friendly way of selecting between different datasets. So maybe this is something we add as a scons param, with some default (uuid? scons command?).
My best guess of how things should work is there should be a dropdown on the top nav bar that lets you select the dataset, and the dataset identifier then becomes a base part of the route. And we could probably have our current CLUSTERS data maps (of cluster ids to cluster metadata) nest under maps with dataset keys.