Closed lidakanari closed 3 years ago
Yes, I think that would be important to be included in NeuroM. If this algorithm is the best we can do to estimate this point by taking into account only the morphometrics of a cell (i.e. without electrical behavior), then we should use it.
Do we have a clear description of an algorithm to do this, and that it means for results to be "correct" or not?
I could write up a scheme of the current algorithm that is used to find the apical point. The problem is we don't have a clear description of the definition of the apical point (from biology). So your second point is practically what we are missing.
It is crucial for the validation of the apical dendrites of the pyramidal cells to be able to extract the morphometrics of the apical tuft and the obliques separately, like section lengths, bifurcation angles, path distances etc.
I have an example in this pull request: https://github.com/BlueBrain/NeuroM/pull/636
Let me know if that helps.
Closing as the issue have been resolved via #636. See https://github.com/BlueBrain/morph-tool/blob/master/morph_tool/apical_point.py for details.
This property is needed for many tasks (synthesizer, morphology release, classification of neurons, validation). The best approximation so far is the function available in Pneumatk, but it still does not give 100% correct results. Could we include this functionality in NeuroM?