-
Notifications
You must be signed in to change notification settings - Fork 26
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
Explain rooted tree vs. "biologically correct" root (curation tool) #524
Comments
This is important for "arbitrary" rooting, since curators are surprised to see this setting after choosing a tree's root. Addresses #524.
This is available for review on devtree. @rgazis, does this address your concerns? |
I'm not too keen on "arbitrary". In fact the root may not be arbitrary - it could actually be the correct one by coincidence, and it is at least likely to b one that is chosen methodically (if 'incorrectly'), not arbitrarily, by an algorithm. I would say in this situation that the correct (biological) root is unknown (to the app), not recorded (in phylesystem), not available (to us), or not curated (by any of our curators). This leads to something like Biological root is |
Thanks, will do. As a bonus, this more accurately reflects the logic of the app. |
These changes are live on devtree for review. |
NOTE that this is causing a problem on devtree. Tree popup disappears immediately from this URL: |
Fixed, merged to master. |
Email from @rgazis:
Even though I rooted the tree (as in the publication) and selected the ingroup. Under trees it says "tree root: arbitrary (not biologically correct)". The same happens with the other studies.
The text was updated successfully, but these errors were encountered: