Trace Editor/Features

From FarsightWiki
(Difference between revisions)
Jump to: navigation, search
(→Feature List)
(→Computed Features and Calculation Parameters)
 
(18 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
= '''Trace Structure''' =
 +
To handle all of the traces the editor uses a tree structure. Neuron branching can be represented as series of points with parents and children. The Inputs Traces to the trace editor can be either SWC, or RPIXML format.
 +
 +
Notes:
 +
Branch point is a Bifurcation, only the Soma should have more than two children.
 +
The traces are divergent from the root of the tree (or the Soma if present). 
 +
 +
== '''RPI XML''' ==
 +
 +
The RPIXML format can be extended to read in extra computed features, that may be specific to a data type or algorithm, by including a header with the features to search for.
 +
 +
<pre>
 +
<FeatureHeaderNames>
 +
  HeadSize,SpineLength,SpineSize,HeadToLengthRatio,DistanceToDendrite,Intensity
 +
</FeatureHeaderNames>
 +
</pre>
 +
Defining the Features to compute in the XML file. The XML file reader will find all traces with associated features which will show in the linked space views.
 +
<pre>
 +
<TraceLine ID="1" Type="1" Parent="-1">
 +
  <TraceBit ID="1" X="0.81" Y="255.81" Z="50.55"/>
 +
</TraceLine>
 +
<!--Dendrite ID=1-->
 +
</pre>
 +
TraceLine 1 is a dendrite (type 1), consisting of 1 trace bit, and has no parent (indicated by the -1).
 +
There are no extra features calculated for this trace.
 +
<pre>
 +
<TraceLine ID="2" Type="5" Parent="1" HeadSize="0.000" SpineLength="7.828" SpineSize="14.000" HeadToLengthRatio="0.000" DistanceToDendrite="1.178" Intensity="146.856">
 +
  <TraceBit ID="1" X="4.00" Y="255.00" Z="50.00"/>
 +
  <TraceBit ID="5" X="3.00" Y="254.00" Z="49.00"/>
 +
  <TraceBit ID="9" X="2.00" Y="254.00" Z="49.00"/>
 +
  <TraceBit ID="13" X="2.00" Y="253.00" Z="48.00"/>
 +
  <TraceBit ID="17" X="2.00" Y="253.00" Z="47.00"/>
 +
  <TraceBit ID="21" X="2.00" Y="253.00" Z="47.00"/>
 +
</TraceLine>
 +
<!--Ending Spine ID=2-->
 +
</pre>
 +
TraceLine 2 is a spine (type 5), consisting of 6 trace bits, and has a parent TraceLine 1.
 +
There are 6 extra features computed and are defined in the Feature Header Names.
 +
 +
The Trace object is built from organizational objects provided to compute and organize features on several levels.
 +
*Trace Object
 +
**Trace Line (id, type, parent id, <Trace Bits>)
 +
***Trace Bit (id, x, y, z, r)
 +
**Trace Gap (Trace Line 1, Trace Line 2)
 +
**Branch Point (Trace Bit, <Trace Lines>)
 +
 +
== '''Trace Bit''' ==
 +
 +
The Trace Bit is the basic unit of the trace structure as a point in 3d space (x,y,z). <br />Each bit also stores the radius and an ID.
 +
 +
== '''Trace Line''' ==
 +
 +
Trace Lines are single trace segments between two critical points that contain an ordered list of trace bits. <br />Each Trace Line has a unique ID. <br />Each stores a pointer to any parents or children(branches). <br />Trace Lines have a type (Soma, dendrite...) that defines its properties.
 +
 +
== '''Trace Object''' ==
 +
 +
The Trace Object is a container of all the traces. <br />This is responsible for  creating the VTK structure, functions modifying the tree structure, and handling file input/output.
 +
 +
== '''Branch Point''' ==
 +
 +
The Branch object is a convenience structure included to help solve branching order problems when the tracer does not know the Proximal/Distal points or the Soma. <br />The data is a Trace Bit and a vector of three or more Trace Lines. <br />Use the set roots command to solve the parent child relationships in the graph structure.
 +
 +
== '''Trace Gap''' ==
 +
 +
A trace gap is an object representing an associative measurement between the smallest separation of the endpoints of two trace Lines. <br />This is used in merging to reconnect fragmented traces.
 +
 
='''Features and algorithms for [[Trace Editor]]'''=
 
='''Features and algorithms for [[Trace Editor]]'''=
  
−
The Trace Editor uses several intrinsic and computed features in both manual and automated processes. Most features used for editing operate on the trace lines or the gap.  
+
The Trace Editor uses several intrinsic and computed features in both manual and automated processes. <br />Most features used for editing operate on the trace lines or the gaps. <br />For specific neural structures such as dendritic spines further features may be computed.  
  
−
='''Feature List'''=
+
[[Image:TraceEditFlow.png|thumb|600px|Basic work flow for how major modules operate. |center]]
  
 +
== '''Intrinsic Features''' ==
 +
*Trace ID:
 +
**The ID is a unique number to look up each trace
 +
*Radius:
 +
** Average Radius of the Trace
 +
*Type:
 +
**The type of neural structure it is
 +
*Parent:
 +
**The ID of the previous Trace in the tree, -1 if it is a root
 +
*Root ID:
 +
**The ID of the first trace of each tree
 +
*Level:
 +
**Following the shortest path of branching how many traces in the tree to reach the root.
 +
*Number of Children
 +
**If it branches how many children if it is not a soma should be 0 or 2
 +
*Is Leaf
 +
** Value is 1 if Trace is a terminal tip
 +
 +
== '''Computed Features and Calculation Parameters''' ==
 +
 
{| border="1px" cellpadding="2" style="text-align:left"
 
{| border="1px" cellpadding="2" style="text-align:left"
 
! Feature
 
! Feature
Line 10: Line 96:
 
! Equation or Variable  
 
! Equation or Variable  
 
|-
 
|-
−
| Gap Size
+
| # of Bits
−
| Minimum distance between endpoints of two traces
+
| How Many points in the Trace
−
| <math>d= \sqrt{(x_1-x_2)^2+(y_1-y_2)^2+(z_1-z_2)^2}</math>
+
| <math> n </math>
−
|-
+
−
| Angle
+
−
| The angle created between two traces normalized as vectors
+
−
| <math> \theta = \arccos(\frac{v_1 \cdot v_2}{|v_1||v_2|}) </math>
+
 
|-
 
|-
 
| Path Length
 
| Path Length
 
| Total length along a trace, indicated by the size of the trace
 
| Total length along a trace, indicated by the size of the trace
−
| <math> L = \sum_{i=0}^{end - 1}\sqrt{(e_ix-e_{i+1}x)^2 + (e_iy-e_{i+1}y)^2+(e_iz-e_{i+1}z)^2} </math>
+
| <math> L = \sum_{i=0}^{n - 1}\sqrt{(e_ix-e_{i+1}x)^2 + (e_iy-e_{i+1}y)^2+(e_iz-e_{i+1}z)^2} </math>
 
|-
 
|-
−
| Euclidean Distance
+
| Euclidean Length
 
| Straight line distance between the endpoints of a trace
 
| Straight line distance between the endpoints of a trace
 
| <math> D = \sqrt{(e_{1x}-e_{2x})^2 + (e_{1y}-e_{2y})^2+(e_{1z}-e_{2z})^2} </math>
 
| <math> D = \sqrt{(e_{1x}-e_{2x})^2 + (e_{1y}-e_{2y})^2+(e_{1z}-e_{2z})^2} </math>
 
|-
 
|-
−
| Fragmentation Smoothness
+
| Tortuousness
−
| Ratio of Path Length to Euclidean Distance <ref name="Ascoli"> Ascoli, Generation,Description and Storage of Dendritic Morphology Data</ref>
+
| Also known as Fragmentation Smoothness or Contraction. Ratio of Path Length to Euclidean Distance <ref name="Ascoli"> Ascoli, Generation,Description and Storage of Dendritic Morphology Data</ref>
 
| <math> s= \frac{L}{D} </math>
 
| <math> s= \frac{L}{D} </math>
 +
|-
 +
| Trace Density
 +
| The Average Spacing of Trace Bits
 +
| <math> \frac{L}{n} </math>
 +
|-
 +
| Volume
 +
| Volume is calculated by the local radius and path length
 +
| <math> V = \sum_{i=0}^{n - 1}\pi (r_i)^2*\sqrt{(e_ix-e_{i+1}x)^2 + (e_iy-e_{i+1}y)^2+(e_iz-e_{i+1}z)^2} </math>
 +
|-
 +
| Distance to parent
 +
| Separation of child traces to the parent
 +
| <math> D_p = \sqrt{(P_{1x}-C_{2x})^2 + (P_{1y}-C_{2y})^2+(P_{1z}-C_{2z})^2} </math>
 +
|-
 +
| Path to Root
 +
| Full path length to root
 +
| <math> \sum_{l=0}^{level}L_l </math>
 +
|-
 +
|
 +
| '''Merging Specific Features'''
 +
|
 +
|-
 +
| Gap Size
 +
| Minimum distance between endpoints of two traces
 +
| <math>d= \sqrt{(x_1-x_2)^2+(y_1-y_2)^2+(z_1-z_2)^2}</math>
 +
|-
 +
| Angle
 +
| The angle created between two traces normalized as vectors
 +
| <math> \theta = \arccos(\frac{v_1 \cdot v_2}{|v_1||v_2|}) </math>
 
|-
 
|-
 
| Maximum Gap Distance
 
| Maximum Gap Distance
Line 48: Line 158:
 
|-
 
|-
 
| Curvature
 
| Curvature
−
| The Hessian matrix for checking branching point existence and interpolating the path. (Still under consideration)
+
| The Hessian matrix for checking branching point existence and interpolating the path.  
 
|<math>  
 
|<math>  
 
\left[\begin{array}{ccc}
 
\left[\begin{array}{ccc}
Line 55: Line 165:
 
  (1-\alpha)f_{xz}(X)  &  (1-\alpha)f_{yz}(X)  &  f_{zz}(X) + \frac{\alpha}{2}f(x)_{xx}(X) +\frac{\alpha}{2}f_{yy}(X)
 
  (1-\alpha)f_{xz}(X)  &  (1-\alpha)f_{yz}(X)  &  f_{zz}(X) + \frac{\alpha}{2}f(x)_{xx}(X) +\frac{\alpha}{2}f_{yy}(X)
 
\end{array} \right]</math>  
 
\end{array} \right]</math>  
−
|-
+
|}
−
| Parent
+
−
| Considering that neurites branching out from the soma form a tree-like structure, a parent point can be used to find a cycle.
+
−
|
+
−
|-
+
−
| Tortuosity
+
−
| Seee section on Tortuosity. Will be up shortly
+
−
|<math>{\displaystyle \mathit{Tor}(f) =  \frac{ \left( \sum_{i=1}^{|f|} \left( \arccos(\phi_{i}) + \Delta_{{\scriptscriptstyle M}}(f_{i-1},f_{i-1}^{p})\right)\right)}{2\left( \frac{\pi}{2}|f| - \pi + \sum_{i=1}^{\frac{|f|}{2}}  \Delta_{{\scriptscriptstyle M}}(\Omega_{i},\Omega_{i}^{p}) \right) }}</math>
+
−
 
+
−
 
+
−
1)<math> f </math>  is a piecewise finite function defined on the interval <math>[a,b]</math>.
+
−
 
+
−
2)<math> |f|\equiv 0 (\mod 4) </math>.
+
  
−
3) For <math>f_{i} \in f </math> the <math> f_{i} </math> are totally ordered such that <math> f_{0}</math> is the first defined point of <math> f </math>  in <math>[a,b]</math>  and <math>f_{|f|}</math>  is the last value defined in <math> [a,b]</math> .
+
'''Cell Features'''
 +
*Segments
 +
**Total number of Traces in the Tree
 +
*Stems
 +
**Number of Processes attached to Soma
 +
*Branch Pt
 +
**How many branches in the cell
 +
*Leaf Nodes
 +
**Total number of terminal tips
 +
*Leaf Level
 +
**Number of compartments in the cells
 +
*Leaf Path Length
 +
**Terminal path length
 +
*Total Euclidean Length
 +
**Sum of all compartment euclidean lengths
 +
*Total Path Length
 +
**Sum of all compartment path lengths
 +
*Average Segment path length
 +
**Average path lengths of the compartments
 +
*Total Volume
 +
**Sum of Volume of each compartment
  
−
4) <math> \phi_{i}</math> is based on the law of cosines, it is <math>\phi_{i} = \frac{\left( D(f_{i-1},f_{i+1})^2 - D(f_{i-1},f_{i})^2 -D(f_{i},f_{i+1})^2 \right)}{-2D(f_{i-1},f_{i})D(f_{i},f_{i+1})}</math>.
+
We are currently working on integrating further with [[L_Measure_functions| L-Measure]]for a more detailed cell analysis.
−
 
+
−
5)<math> \Delta_{{\scriptscriptstyle M}}(f_{i-1},f_{i-1}^{p}) = \left| D(f_{i-1},M) - D(f_{i-1}^{p},M) \right| </math>.
+
−
 
+
−
6)<math>M</math> is the midpoint of the line between <math>f_{0}</math> and <math>f_{|f|}</math>.
+
−
 
+
−
7)<math>f_{i-1}^{p}</math> is <math>f_{i-1}</math> projected onto the line thru <math>f_{0}</math> and <math>f_{|f|}</math>
+
−
 
+
−
8)<math>\Omega_{i} = \left( r\cos(\frac{2\pi i}{|f|}) + M_{x}', r\sin(\frac{2\pi i}{|f|}) + M_{y}' \right)</math>.
+
−
 
+
−
9) <math>r = \frac{D(f_{0}, f_{|f|})}{4}</math>.
+
−
 
+
−
10)<math>M'</math> is the midpoint of the line between <math>f_{0}</math> and <math>M</math>.
+
−
 
+
−
11)<math>\Omega_{i}^{p} = \left( r\cos(\frac{2\pi i}{|f|}) + M_{x}', M_{y}' \right) </math>
+
−
 
+
−
|}
+
  
 
='''Algorithms'''=
 
='''Algorithms'''=
−
The algorithms suggested are used to control the editing process allowing for rule based cluster editing. The Goal is to complete group editing in five steps.
 
−
[[Image:Edit_Operations.png|800px|thumb|center|Proposed steps of editing ]]
 
−
 
 
   
 
   
 
== '''Merge Small Gaps''' ==
 
== '''Merge Small Gaps''' ==
Line 100: Line 199:
  
 
*Minimal distance between end points
 
*Minimal distance between end points
−
**[[Angle between traces-]] The angle is measured between the two traces by computing the [http://en.wikipedia.org/wiki/Vector_norm norm of their vectors] and the [http://en.wikipedia.org/wiki/Dot_product dot product]. <br />The equation is:  <math>v_1 \cdot v_2 = |v_1||v_2| \cos(\theta)</math> which when solved for <math>\theta</math> is: <math> \theta = \arccos(\frac{v_1 \cdot v_2}{|v_1||v_2|}) </math>  
+
**'''Angle between traces''' The angle is measured between the two traces by computing the [http://en.wikipedia.org/wiki/Vector_norm norm of their vectors] and the [http://en.wikipedia.org/wiki/Dot_product dot product]. <br />The equation is:  <math>v_1 \cdot v_2 = |v_1||v_2| \cos(\theta)</math> which when solved for <math>\theta</math> is: <math> \theta = \arccos(\frac{v_1 \cdot v_2}{|v_1||v_2|}) </math>  
−
**[[Path length-]] The path length is considered if the end points are not the best fit for the merge.  For instance, a merging that would cause a sharp peak in the neurite.  This is a more serious problem for large gaps (see below).  To help alleviate this for small gaps, merge at the point where the direction changes sharply.   
+
**'''Path length''' The path length is considered if the end points are not the best fit for the merge.  For instance, a merging that would cause a sharp peak in the neurite.  This is a more serious problem for large gaps (see below).  To help alleviate this for small gaps, merge at the point where the direction changes sharply.   
−
**[[Gap distance is too large-]] The distance between the two points e_1, e_2  is computed to save computation.  If the distance is longer than the excepted small gap distance, then the traces will not be considered for merging.  A cost function adapted from "Automated Three-Dimensional Tracing of Neurons in Confocal and Brightfield Images" will take into account small gaps with two end points.
+
**Gap distance is too large The distance between the two points e_1, e_2  is computed to save computation.  If the distance is longer than the excepted small gap distance, then the traces will not be considered for merging.  A cost function adapted from "Automated Three-Dimensional Tracing of Neurons in Confocal and Brightfield Images" will take into account small gaps with two end points.
−
**[[Consider possibility of loops]] Though less probable in 3D, often there are 2D projections of 3D images resulting in loops being in the images. Loops in the branching structure can be avoided by checking the parents, as a trace cannot have two parents, but there can be two children.  
+
**Consider possibility of loops Though less probable in 3D, often there are 2D projections of 3D images resulting in loops being in the images. Loops in the branching structure can be avoided by checking the parents, Each of the trace Lines should have unique root nodes.  
−
[[Image:problem_graph.jpeg|200px|thumb|right| Two neurites that might cause a problem for the merging minor gaps algorithm.]]
+
 
*Another trace is a better fit (Cost Function)
 
*Another trace is a better fit (Cost Function)
 
**Smallest gap
 
**Smallest gap
Line 118: Line 216:
  
 
  Goal: Connect Large gaps that step 1 cannot  simply connect by addition of a  single cell
 
  Goal: Connect Large gaps that step 1 cannot  simply connect by addition of a  single cell
−
  Method: Larger gaps need new segments created, <br />new Trace Bits must be added, <br />smoothing operator.
+
  Method: Larger gaps need new segments created, <br />new Trace Bits must be added using manual tracing in the 3D cursor toolbox
  
 
[[Image:MergingBranching.gif|800px|thumb|right|Example showing how Merging and branching are interconnected. The Merging that creates sharp turns needs to be smoothed. The Traces need to create a new branch point and trace bits to interpolate the original path of the branch. ]]
 
[[Image:MergingBranching.gif|800px|thumb|right|Example showing how Merging and branching are interconnected. The Merging that creates sharp turns needs to be smoothed. The Traces need to create a new branch point and trace bits to interpolate the original path of the branch. ]]
−
 
−
*Curve fitting to find trend of:
 
−
**Direction
 
−
**Curvature
 
−
*Interpolation
 
−
**Extend the line
 
−
**Most probable vector
 
−
**Avoid  creating edges
 
  
 
   
 
   

Latest revision as of 20:14, 15 April 2011

Contents

Trace Structure

To handle all of the traces the editor uses a tree structure. Neuron branching can be represented as series of points with parents and children. The Inputs Traces to the trace editor can be either SWC, or RPIXML format. 

Notes: 
Branch point is a Bifurcation, only the Soma should have more than two children. 
The traces are divergent from the root of the tree (or the Soma if present).

RPI XML

The RPIXML format can be extended to read in extra computed features, that may be specific to a data type or algorithm, by including a header with the features to search for. 

<FeatureHeaderNames>
  HeadSize,SpineLength,SpineSize,HeadToLengthRatio,DistanceToDendrite,Intensity
</FeatureHeaderNames>

Defining the Features to compute in the XML file. The XML file reader will find all traces with associated features which will show in the linked space views. 

<TraceLine ID="1" Type="1" Parent="-1">
  <TraceBit ID="1" X="0.81" Y="255.81" Z="50.55"/>
</TraceLine>
<!--Dendrite ID=1-->

TraceLine 1 is a dendrite (type 1), consisting of 1 trace bit, and has no parent (indicated by the -1). There are no extra features calculated for this trace. 

<TraceLine ID="2" Type="5" Parent="1" HeadSize="0.000" SpineLength="7.828" SpineSize="14.000" HeadToLengthRatio="0.000" DistanceToDendrite="1.178" Intensity="146.856">
  <TraceBit ID="1" X="4.00" Y="255.00" Z="50.00"/>
  <TraceBit ID="5" X="3.00" Y="254.00" Z="49.00"/>
  <TraceBit ID="9" X="2.00" Y="254.00" Z="49.00"/>
  <TraceBit ID="13" X="2.00" Y="253.00" Z="48.00"/>
  <TraceBit ID="17" X="2.00" Y="253.00" Z="47.00"/>
  <TraceBit ID="21" X="2.00" Y="253.00" Z="47.00"/>
</TraceLine>
<!--Ending Spine ID=2-->

TraceLine 2 is a spine (type 5), consisting of 6 trace bits, and has a parent TraceLine 1. There are 6 extra features computed and are defined in the Feature Header Names.

The Trace object is built from organizational objects provided to compute and organize features on several levels.

  • Trace Object
    • Trace Line (id, type, parent id, <Trace Bits>)
      • Trace Bit (id, x, y, z, r)
    • Trace Gap (Trace Line 1, Trace Line 2)
    • Branch Point (Trace Bit, <Trace Lines>)

Trace Bit 

The Trace Bit is the basic unit of the trace structure as a point in 3d space (x,y,z). 
Each bit also stores the radius and an ID.

Trace Line 

Trace Lines are single trace segments between two critical points that contain an ordered list of trace bits. 
Each Trace Line has a unique ID. 
Each stores a pointer to any parents or children(branches). 
Trace Lines have a type (Soma, dendrite...) that defines its properties.

Trace Object 

The Trace Object is a container of all the traces. 
This is responsible for  creating the VTK structure, functions modifying the tree structure, and handling file input/output.

Branch Point 

The Branch object is a convenience structure included to help solve branching order problems when the tracer does not know the Proximal/Distal points or the Soma. 
The data is a Trace Bit and a vector of three or more Trace Lines. 
Use the set roots command to solve the parent child relationships in the graph structure.

Trace Gap 

A trace gap is an object representing an associative measurement between the smallest separation of the endpoints of two trace Lines. 
This is used in merging to reconnect fragmented traces.

Features and algorithms for Trace Editor

The Trace Editor uses several intrinsic and computed features in both manual and automated processes.
Most features used for editing operate on the trace lines or the gaps.
For specific neural structures such as dendritic spines further features may be computed.

Basic work flow for how major modules operate.

Intrinsic Features

  • Trace ID:
    • The ID is a unique number to look up each trace
  • Radius:
    • Average Radius of the Trace
  • Type:
    • The type of neural structure it is
  • Parent:
    • The ID of the previous Trace in the tree, -1 if it is a root
  • Root ID:
    • The ID of the first trace of each tree
  • Level:
    • Following the shortest path of branching how many traces in the tree to reach the root.
  • Number of Children
    • If it branches how many children if it is not a soma should be 0 or 2
  • Is Leaf
    • Value is 1 if Trace is a terminal tip

Computed Features and Calculation Parameters

Feature Description Equation or Variable
# of Bits How Many points in the Trace n
Path Length Total length along a trace, indicated by the size of the trace L = \sum_{i=0}^{n - 1}\sqrt{(e_ix-e_{i+1}x)^2 + (e_iy-e_{i+1}y)^2+(e_iz-e_{i+1}z)^2}
Euclidean Length Straight line distance between the endpoints of a trace D = \sqrt{(e_{1x}-e_{2x})^2 + (e_{1y}-e_{2y})^2+(e_{1z}-e_{2z})^2}
Tortuousness Also known as Fragmentation Smoothness or Contraction. Ratio of Path Length to Euclidean Distance [1] s= \frac{L}{D}
Trace Density The Average Spacing of Trace Bits \frac{L}{n}
Volume Volume is calculated by the local radius and path length V = \sum_{i=0}^{n - 1}\pi (r_i)^2*\sqrt{(e_ix-e_{i+1}x)^2 + (e_iy-e_{i+1}y)^2+(e_iz-e_{i+1}z)^2}
Distance to parent Separation of child traces to the parent D_p = \sqrt{(P_{1x}-C_{2x})^2 + (P_{1y}-C_{2y})^2+(P_{1z}-C_{2z})^2}
Path to Root Full path length to root \sum_{l=0}^{level}L_l
Merging Specific Features
Gap Size Minimum distance between endpoints of two traces d= \sqrt{(x_1-x_2)^2+(y_1-y_2)^2+(z_1-z_2)^2}
Angle The angle created between two traces normalized as vectors \theta = \arccos(\frac{v_1 \cdot v_2}{|v_1||v_2|})
Maximum Gap Distance The maximum distance between endpoints that can be merged Δ
Weights The weights are used in the cost1 algorithm α β
Cost1 Weighted scalar evaluating the merge [2] C_1=\alpha\frac{\theta}{\pi}+\beta\frac{d}{\Delta}
Cost2 Weighted scalar with Fragmentation Smoothness C_2=\theta[\frac{d}{\Delta}]s
Curvature The Hessian matrix for checking branching point existence and interpolating the path. \left[\begin{array}{ccc} f(x)_{xx}(X) + \frac{\alpha}{2}f_{yy}(X) + \frac{\alpha}{2}f_{zz}(X) & (1-\alpha)f_{xy}(X) & (1-\alpha)f_{xz}(X) \\ (1-\alpha)f_{xy}(X) & f_{yy}(X) + \frac{\alpha}{2}f(x)_{xx}(X) +\frac{\alpha}{2}f_{zz}(X) & (1-\alpha)f_{yz}(X) \\ (1-\alpha)f_{xz}(X) & (1-\alpha)f_{yz}(X) & f_{zz}(X) + \frac{\alpha}{2}f(x)_{xx}(X) +\frac{\alpha}{2}f_{yy}(X) \end{array} \right]

Cell Features

  • Segments
    • Total number of Traces in the Tree
  • Stems
    • Number of Processes attached to Soma
  • Branch Pt
    • How many branches in the cell
  • Leaf Nodes
    • Total number of terminal tips
  • Leaf Level
    • Number of compartments in the cells
  • Leaf Path Length
    • Terminal path length
  • Total Euclidean Length
    • Sum of all compartment euclidean lengths
  • Total Path Length
    • Sum of all compartment path lengths
  • Average Segment path length
    • Average path lengths of the compartments
  • Total Volume
    • Sum of Volume of each compartment

We are currently working on integrating further with L-Measurefor a more detailed cell analysis.

Algorithms

Merge Small Gaps 

Goal: Create longest continuous trace segments by merging close endpoints
Methods: Nearest neighbors  (Closest end points), 
Rejection based on conflicts and thresholds
  • Minimal distance between end points
    • Angle between traces The angle is measured between the two traces by computing the norm of their vectors and the dot product.
      The equation is: v_1 \cdot v_2 = |v_1||v_2| \cos(\theta) which when solved for θ is: \theta = \arccos(\frac{v_1 \cdot v_2}{|v_1||v_2|})
    • Path length The path length is considered if the end points are not the best fit for the merge. For instance, a merging that would cause a sharp peak in the neurite. This is a more serious problem for large gaps (see below). To help alleviate this for small gaps, merge at the point where the direction changes sharply.
    • Gap distance is too large The distance between the two points e_1, e_2 is computed to save computation. If the distance is longer than the excepted small gap distance, then the traces will not be considered for merging. A cost function adapted from "Automated Three-Dimensional Tracing of Neurons in Confocal and Brightfield Images" will take into account small gaps with two end points.
    • Consider possibility of loops Though less probable in 3D, often there are 2D projections of 3D images resulting in loops being in the images. Loops in the branching structure can be avoided by checking the parents, Each of the trace Lines should have unique root nodes.
  • Another trace is a better fit (Cost Function)
    • Smallest gap
    • Better Angular alignment
  • "Bad merge"
    • The merge causes corners
    • Needs to be smoothed
Illustration of reconnecting fragmented structures using a cost algorithm on the critical points. The critical points 'a' and 'b' are merged because the cost C(a,b) is less than the cost of merging other points. Point 'd' is rejected because its gap distance is beyond the threshold.[2]

The Cost function we have implemented is modified from:
C_1=\alpha\frac{\theta}{\pi}+\beta\frac{d}{\Delta}
to include fragmentation smoothness. The original function had user selectable weights α,β to scale the effects of the gap distance and angle of the merge. The Fragmentation smoothness is the ratio of the path distance to the end point displacement. If the merged traces start forming a "U" shape or a loop it would result in a higher cost. A second alteration is to multiply the factors so that the outliers are further differentiated from the more probable traces. The resulting formula:
C_2=\theta[\frac{d}{\Delta}]s
accounts for the three factors of angle, gap distance, and smoothness of the trace.

Interpolate Large Gaps 

Goal: Connect Large gaps that step 1 cannot  simply connect by addition of a  single cell
Method: Larger gaps need new segments created, 
new Trace Bits must be added using manual tracing in the 3D cursor toolbox
Example showing how Merging and branching are interconnected. The Merging that creates sharp turns needs to be smoothed. The Traces need to create a new branch point and trace bits to interpolate the original path of the branch.


Branch Points 

Goal: Detect and control Branching
Method: Detect most probable intercepts, 
Determination of main branch and child, 
Type of branch point
  • Distance maps
    • Nearest neighbors (traces)
    • Closest trace bits
  • Angle of intercept
  • Interpolation

Detect most probable intercepts: So far most of the methods I have evaluated or developed require information about the intensities in order to compute the most probable intercept. The reasoning behind this is the direction of the child branch does not give information about the intercept over long distances. In the short distance branching case, it is more acceptable to use the direction to figure out the interception point. The child branch would have to curve faster( over a shorter distance) if the direction of the branch was not in line with the main branch. In the case of a large gap between the main and child branch the child can curve slowly and still reach the main branch. This means that when there is a large gap there is more variation in the location of the intersection. So, to determine the proper intersection we can use the H(x) matrix listed in the features. I think when the gap is small( not sure what this is yet) we can just fill with a shortest distance line.

Soma Detection 

Goal: Correspond processes with a soma
Method: Segmentation of original data, 
Localize the area to attach processes to soma, 
Correct direction of traces
  • Image intensity
  • Blob segmentation
  • Centroid
  • Distance map
  • Connectivity
    • Connected components
    • Localization of processes
Illustration of how the processes should be connected to a soma(shown in red).
The Dendrites are shown in blue, where the axon is shown in yellow.


Fragments 

Goal: Removal of small traces that do not correspond to a process
Method: Small traces removed, 
Leftovers from splitting operators, 
Line fragments that cannot be merged
  • Lowest percentile of length
    • Traces with no parents or children
    • Type dependent

References

  1. ↑ Ascoli, Generation,Description and Storage of Dendritic Morphology Data
  2. ↑ 2.0 2.1 Wenyun He, Automated Three-Dimensional Tracing of Neurons in Confocal and Brightfield Images
Retrieved from "http://farsight-toolkit.ee.uh.edu/wiki/Trace_Editor/Features"
Personal tools