Replies: 1 comment 2 replies
-
Thanks for writing this up! One clarification to anybody reading this: In the text above, the word All the best |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
After communication with one of Jaxley's developers Michael, here is my brief understanding of the assignment behavior.
Jaxley calles a series of nodes with no branching a "branch". For example, [branching-3-4-5-6-branching], [3-4-5-6] is considered a branch. If we specify ncomp = 1, generally one branch corresponds to one compartment. Thus in general, compartment is not just [node1-node2], but a series of nodes ! It is not direct mapping between SWC file and compartment
Furthermore, branches might be interrupted. Quoting Michael's words:
"This happens when the swc files traces a branch with interruptions from other branches (e.g. the person tracing the neuron traces branch 5, but then stops to trace branch 28, and then returns to trace branch 5. In that case, the “5” branch will be split into two subbranches in Jaxley). We might change this behavior in the future."
So it is quite hard to trace the assignment behavior by writing a "reverse-engineering algorithm" by oneself.
We can, however, use cell.xyzr[] function. This attribute saves all the swc coordinates by the branch that they are assigned to. For example,
cell.xyzr[5]
will show you all SWC coordinates that are merged intocell.branch(5)
. One can also map .xyzr to SWC file by mapping nodes with exactly same coordinate (if one hopes to get the node-to-node topology/parent-children relationship).Beta Was this translation helpful? Give feedback.
All reactions