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
I sometimes don't have internet and would like to visualise a .nwk tree using Auspice.
When I start an auspice session with npx auspice@latest view --datasetDir . I can't seem to be able to just drop the .nwk tree.
What am I doing wrong? Is it possible to visualise nwks at all like this?
Would it be possible to enable drag-and-drop if you run auspice locally?
I know this isn't of interest to most folks since you can always go to auspice.us (if you have internet) - but this would be a nice feature for dev folks etc.
The text was updated successfully, but these errors were encountered:
drag-and-drop of datasets is specifically a functionally of auspice.us and not Auspice. Auspice only allows dragging on additional metadata for a displayed dataset.
The way I've been thinking of auspice is like so: the unmodified auspice client is the tree viewer which certain other projects import and extend. So auspice.us extends it with a custom splash page with drag-and-drop functionality. If we were to build that functionality into auspice itself then we'd be enabling it for the projects which use auspice, which is not always a good thing.
Nextstrain.org actually uses its own custom splash page so it'd wouldn't be a problem there. If there's demand for this feature I don't think it's unreasonable.
Context
I sometimes don't have internet and would like to visualise a
.nwk
tree using Auspice.When I start an auspice session with
npx auspice@latest view --datasetDir .
I can't seem to be able to just drop the.nwk
tree.What am I doing wrong? Is it possible to visualise
nwk
s at all like this?Would it be possible to enable drag-and-drop if you run auspice locally?
I know this isn't of interest to most folks since you can always go to auspice.us (if you have internet) - but this would be a nice feature for dev folks etc.
The text was updated successfully, but these errors were encountered: