Closed chalimou closed 8 years ago
Could you specify what you mean by "section path"? You can edit your post to add more information.
The section path distance is the neurite length from soma to the end of the section. It is measured by the feature section_path_distances in NeuroM. The section radial distance is the euclidean distance from the soma to the end of the section given by section_radial_distances in NeuroM. If I can be sure that for a given cell the elements of the section_path_distances and section_radial_distances correspond one-to-one, that is for example, the 23rd element of the two lists refer to the same section, I can compute the ratios section_path_distances/section_radial_distances by element. This is the tortuosity by definition.
Yes, the iteration order for section functions is the same, so you can take the ratio.
great, thanks, the confirmation was what I needed. nancy
On 16 Mar 2016, at 10:01, Juan Palacios notifications@github.com wrote:
Yes, the iteration order for section functions is the same, so you can take the ratio.
— You are receiving this because you authored the thread. Reply to this email directly or view it on GitHub https://github.com/BlueBrain/NeuroM/issues/281#issuecomment-197217992
Tortuosity is defined as the ratio of the section path to the section radial distance and reflects the "curvature" of the neurite. It is an essential feature for the synthesis process and its validation, as well as the general evaluation of synthesised cells. I think it is useful to have it as a feature in order to avoid user errors. The tortuosity can be computed since the features involved (section path and radial distances) already exist in NeuroM. But if and only if their values are in an one-to-one correspondence. Are they?