scikit-bio
scikit-bio copied to clipboard
Refactor TreeNode
Users have a consistent Tree API
- [ ] Handle linkage matrices (#346)
- [ ] Have an equals method (#465)
- [ ] Consistent handling of missing data (#791)
- [ ] Tree operations shouldn't care where they are (#807)
- [ ] Think about taxonomy representations
Potentially use NetworkX internally.
Past discussion available at (#218)
What would the scope of this be? I'm not too familiar with NetworkX. It looks like it's mostly used to represent graph objects, right? Is there a way to only use NetworkX's node implementation as the backend for TreeNode and leave the interface the same, or am I completely missing the point?
I've got a use-case that requires a networkx representation of the TreeNode object. Can submit pull request shortly
to_networkx and from_networkx would be very nice to have, thank you!!