You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add .to_graph() and .from_graph() methods. See below. This is a long term thing though.
I agree, these things would be awesome to have, but I think we should add all of this functionality separately. Maybe in jaxley.graph_utils or something. Then the user could resample, clean, fix, edit, etc. however he wants directly on the graph. We could add a to_graph and from_graph method, that casts module.nodes to a networkxDiGraph object. Then graph_utils could operate on that.
I.e. read swc into networkxDiGraph before running cell = Cell.from_graph(swc_graph) or something? Should work I think. MorphoPy does something like this.
Yes it would be great if we could entirely remove my hand-written SWC reader. I would be open to use MorphoPy for this, or just networkx (not sure what is easier, I know neither of those two libraries well). The features we need are:
automatically reconstruct parents (i.e. the branch structure)
get length and radius of every reconstructed point in every branch
get the type of every branch
Anyways, let's maybe talk about this next week before starting to tackle it, but I think it could be worth it.
Add
.to_graph()
and.from_graph()
methods. See below. This is a long term thing though.Originally posted by @jnsbck in #238 (comment)
The text was updated successfully, but these errors were encountered: