-
Notifications
You must be signed in to change notification settings - Fork 33
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
NeuronConnector class for connectivity of TreeNeurons #119
Conversation
This looks useful! I guess the main use case are CATMAID neurons for now? Given that it requires meaningful connector IDs I would suggest making a note in the docstring. Perhaps even a sanity check that throws a warning if a neuron is added with sequential connector IDs? I'd also add the |
Docs added, including documenting the fact that connector IDs need to be consistent between neurons, and raising a warning every time a connector ID seems to have more than one input. Needs some test data, though, I think. |
Hi Chris. Sorry, I lost track of this. Happy to merge if ready? |
- the old implementation led to a int->float->int conversion which caused 64bit integer IDs to be mangled - also add warning about non-numeric source/target IDs
- fix bug that prevent it from running - add second method "majority"
... looking up all segments at once
…ant the first one.
Plotting an empty TreeNeuron previously threw an `AttributeError`: ``` empty_skel = navis.TreeNeuron(None) navis.plot3d(empty_skel) ```
Plotting an empty TreeNeuron previously threw an `AttributeError`: ``` empty_skel = navis.TreeNeuron(None) navis.plot3d(empty_skel) ```
I've added an integration test so I'm happy that it works now. The merge log looks pretty whacky, though, it's claiming responsibility for a bunch of older commits, possibly because of a rebase. |
Superceded by #133 |
For converting a bag of neurons with possibly-intersecting connector nodes into a graph or adjacency matrix.