2011 Winter Project Week:TwoTensorTracts - Revision history

Lauren: /* Delivery Mechanism */

2011-01-14T18:07:36Z

Delivery Mechanism

2011-01-14T18:07:19Z

Delivery Mechanism

2011-01-14T18:06:53Z

Thank You

2011-01-14T17:38:02Z

2011-01-14T17:37:37Z

2011-01-14T17:35:14Z

Thank You

2011-01-14T17:33:11Z

2011-01-14T17:30:59Z

Key Investigators

2011-01-14T17:29:02Z

Key Investigators

2011-01-14T17:28:14Z

Key Investigators

@@ Line 51: / Line 51: @@
 #ITK Module
 #Slicer Module YES
-##Built-in
+##Built-in YES!
 ##Extension -- commandline
 ##Extension -- loadable

@@ Line 50: / Line 50: @@
 #ITK Module
-#Slicer Module
+#Slicer Module YES
 ##Built-in
 ##Extension -- commandline

@@ Line 36: / Line 36: @@
 <h3>Progress</h3>
-* Learned about Slicer4 module creation in c++ and python.
+* Installed/tested 2-tensor slicer3 python module. Thank you Demian for help. Reported bug with voxel sizes to Yogesh Rathi.
 * Converted clustering output tcl script to output slicer3/slicer4 MRML format
 * Initial work on porting slicer2 ModelInteraction module to slicer4. Module will enable interactive model selection/grouping/naming. Slicer4 picking and improved model hierarchy functionality will be used when available.  The module is a QTScriptedModule python Slicer4 implementation.

@@ Line 4: / Line 4: @@
 Image:wholebrainclustersexample.jpg|Example whole brain clustering result.
 Image:example2tensortracts.jpg|Example two-tensor tractography result.
-Image:clustersinSlicer4.png|Progress:Cluster output loaded into Slicer4 with new MRML file.
+Image:clustersinSlicer4.png|Progress: Cluster output loaded into Slicer4 with new MRML file.
-Image:modelHierarchyClustersSlicer4.png|Progress:Model hierarchy created by initial Slicer4 module
+Image:modelHierarchyClustersSlicer4.png|Progress: Model hierarchy created by initial Slicer4 module
 </gallery>

@@ Line 4: / Line 4: @@
 Image:wholebrainclustersexample.jpg|Example whole brain clustering result.
 Image:example2tensortracts.jpg|Example two-tensor tractography result.
-Image:clustersinSlicer4.png|Cluster output loaded into Slicer4 with new MRML file.
+Image:clustersinSlicer4.png|Progress:Cluster output loaded into Slicer4 with new MRML file.
 </gallery>

@@ Line 8: / Line 8: @@
 ==Key Investigators==
 * BWH: Lauren O'Donnell, Yogesh Rathi, C-F Westin
 <div style="margin: 20px;">
@@ Line 32: / Line 36: @@
 * installed/tested 2-tensor slicer3 python module. Thank you Demian for help. Reported bug with voxel sizes to Yogesh Rathi.
 * Converted clustering output tcl script to output slicer3/slicer4 MRML format
-* Initial work on porting slicer2 ModelInteraction module to slicer4. Module will enable interactive model selection/grouping/naming. Slicer4 picking and improved model hierarchy functionality will be used when available.
+* Initial work on porting slicer2 ModelInteraction module to slicer4. Module will enable interactive model selection/grouping/naming. Slicer4 picking and improved model hierarchy functionality will be used when available.  The module is a QTScriptedModule python Slicer4 implementation.
 * Some progress towards general file formats as input to clustering code, to allow slicer2/3/4/other programs to input tract files (one or many vtk's)
 </div>

@@ Line 21: / Line 21: @@
 <h3>Approach, Plan</h3>
-Our goals for the project week are to update clustering I/O to read tracts as a single large polydata file per subject, and to produce output in Slicer3 MRML format.
+Our goals for the project week are to test 2-tensor tractography, to update clustering I/O to read tracts as a single large polydata file per subject, and to produce output in Slicer3 MRML format.
 The next step is to ascertain what needs to be done to visualize/label the clusters in slicer3 or 4. This is in order to make atlases or study a particular tract. The old slicer2 interface allowed interactive selection of clusters (show/hide selected, and show/hide labeled or unlabeled) and anatomical naming/labeling.