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

report tree retrieval separate from rendering #338

Open
3 tasks done
arlin opened this issue Aug 30, 2018 · 0 comments
Open
3 tasks done

report tree retrieval separate from rendering #338

arlin opened this issue Aug 30, 2018 · 0 comments
Assignees

Comments

@arlin
Copy link
Member

arlin commented Aug 30, 2018

The stress test today reveals that the portal sometimes fails to render a tree, or delays for a very long time. During this time, the user actually can access the tree using Export as, but the user does not know this. The scaled trees may become accessible also. The tree retrieval message does not appear until after the tree has been rendered.

  • Notify the user as soon as the tree is retrieved.
  • Update the notification message to indicate that the tree is being rendered. "A tree with X tips has been retrieved. You can get the Newick string with Export as: Newick. A graphical view will appear below."
  • Update the tip count for the unscaled tree as soon as the unscaled tree has been retrieved. Do not use ETE to count the tips. Use DendroPy or something else.
@arlin arlin added the ready label Aug 30, 2018
@arlin arlin added this to the Phylotastic general manuscript milestone Aug 30, 2018
ducvan0212 pushed a commit that referenced this issue Sep 6, 2018
@arlin arlin removed this from the Phylotastic general manuscript milestone Sep 17, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants