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

ENH: Allow dropping of trees in local version of auspice #1544

Open
corneliusroemer opened this issue Sep 16, 2022 · 3 comments
Open

ENH: Allow dropping of trees in local version of auspice #1544

corneliusroemer opened this issue Sep 16, 2022 · 3 comments
Labels
enhancement New feature or request

Comments

@corneliusroemer
Copy link
Member

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 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.

@joverlee521
Copy link
Contributor

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.

If you want to do drag-and-drop locally, I would recommend running auspice.us locally.

@corneliusroemer
Copy link
Member Author

I see, what's the reason for that limitation?

Is it possible to npm install auspice.us?

The docs suggest a condo environment which is quite heavy.

@jameshadfield
Copy link
Member

I see, what's the reason for that limitation?

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
No open projects
Status: Backlog
Development

No branches or pull requests

3 participants