2010 Summer Project Week EMSegmentation kmeans - Revision history

Priya at 14:14, 25 June 2010

2010-06-25T14:14:10Z

2010-06-25T13:59:15Z

2010-06-25T13:58:40Z

2010-06-18T01:35:43Z

2010-06-04T20:54:29Z

2010-06-04T20:51:09Z

2010-06-04T20:49:27Z

2010-06-04T20:49:14Z

@@ Line 26: / Line 26: @@
 <h3>Progress</h3>
-Met with Kilian and went over the current processing pipeline with the Python codes we have and got an understanding of how we should proceed in order to integrate into Slicer 3.6. Will work out the details in the coming weeks. Worked on the Python codes to make it more easy to integrate into Slicer 3.6.
+Met with Kilian and went over the current processing pipeline with the stand alone Python codes and now have a general understanding of how we should proceed in order to integrate into Slicer 3.6. Will work out the details in the coming weeks. Based on Kilian's suggestions, modified the Python codes to make it more easy to integrate into Slicer 3.6.
 </div>

@@ Line 26: / Line 26: @@
 <h3>Progress</h3>
-Met with Kilian and went over the current processing pipeline with the Python codes we have and got an understanding of how we should proceed in order to integrate into Slicer 3.6. Will work more in detail in the coming weeks. Worked on the Python codes to make it more easy to integrate into Slicer 3.6.
+Met with Kilian and went over the current processing pipeline with the Python codes we have and got an understanding of how we should proceed in order to integrate into Slicer 3.6. Will work out the details in the coming weeks. Worked on the Python codes to make it more easy to integrate into Slicer 3.6.
 </div>

@@ Line 26: / Line 26: @@
 <h3>Progress</h3>
-Will be updated ...
+Met with Kilian and went over the current processing pipeline with the Python codes we have and got an understanding of how we should proceed in order to integrate into Slicer 3.6. Will work more in detail in the coming weeks. Worked on the Python codes to make it more easy to integrate into Slicer 3.6.
 </div>

@@ Line 25: / Line 25: @@
 <h3>Progress</h3>
-Will be updated
+Will be updated ...
 </div>

@@ Line 5: / Line 5: @@
 ==Key Investigators==
-* Priya Srinivasan, Daniel Haehn, Kilian Pohl, Sylvain Bouix
+* BWH: Priya Srinivasan, Daniel Haehn, Sylvain Bouix
 <div style="margin: 20px;">
 <div style="width: 27%; float: left; padding-right: 3%;">

@@ Line 17: / Line 17: @@
 <h3>Approach, Plan</h3>
-Currently we have stand alone python scripts that take in 3 inputs: a template MRML scene, path to the T1 image, path to the atlas images. Intensities are computed using KMeans and a MRML scene is outputted which can directly be loaded in Slicer3 for segmentation. Registration of images (T1 and atlases) has to be done as a preprocessing step before providing as inputs to the python scripts. Meet up during NAMIC week and see how best this process can be integrated as one of the options with the current EMSegmentation pipeline in Slicer3.
+Currently we have stand alone python scripts that take in 3 inputs: a template MRML scene, path to the T1 image, path to the atlas images. Intensities are computed using KMeans and a MRML scene is outputted which can directly be loaded in Slicer3 for segmentation. Registration of images (T1 and atlases) has to be done as a preprocessing step before providing as inputs to the python scripts. Meet up during NAMIC week and see how best this process can be integrated as one of the options in the current EMSegmentation pipeline in Slicer3.
   </div>