-
Notifications
You must be signed in to change notification settings - Fork 4
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
ouchtree - how many terminal nodes under each internal node? #8
Comments
The The resulting data frame is pretty self-explanatory. Each node (internal or terminal) gets a line. That line contains the following information: the name of the node, the name of its immediate ancestor, its time (the positive direction being the future), and an optional label. |
Aloha @soungalo As Aaron says ouchtree does not have accessor functions for returning descendants, etc. But if you want to see the internal components, you can use the
and access the elements by name (or other standard methods) on the return object of attributes(). However, there are other packages that have treewalking functions such as Marguerite |
I an not sure what youʻre doing, but if you want to get it your tree back into
|
Thank you both!
I should have probably mentioned that the ouch tree was created using the convertTreeData function from SURFACE, so there might be something weird with the object I'm working with. In any case, it sounds like the easy way would be to go back to the original tree (phylo class) and work with it. |
`ape2ouch( phylo_tree )` works just fine.
|
How about |
Could you please provide some guidelines on working with ouchtree objects?
I'm trying to loop on all internal nodes and determine the number of terminal nodes under each. How can this be achieved?
The text was updated successfully, but these errors were encountered: