-
Notifications
You must be signed in to change notification settings - Fork 27
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
Default: update.tree = TRUE #661
Comments
Also update examples and OMA to reflect this new default choice |
How about the node labels? |
Not sure if I answer to your question, but the names of tree nodes are not updated. The pruning is done internally by utilizing Line 494 in 2dc3430
|
What I meant was whether it would make sense to also update node labels so that the user could, by default, avoid cryptic errors like this:
Error: Incompatible tree and abundance table! Please try to provide 'node.label'. |
Ahh, yes. It should be relatively easy to do that. And I think this is good idea. Related to |
Sounds like a good idea! |
Just as a note, the cryptic error doesn't go away when using
|
Yep, that is because the names of nodes are not updated even though the tree is pruned |
And based on the above discussion the consensus seems to be to change this so that also node labels would be updated by default. |
Agglomeration and subsetting functions have
update.tree
parameter that controls whether to simplify the the tree to correspond the data after agglomeration/subsetting. The default choice should be that the tree is updated, i.e.,update.tree = TRUE
.The text was updated successfully, but these errors were encountered: