Summer2009:VCFS - Revision history

Jvs at 14:52, 27 June 2009

2009-06-27T14:52:23Z

2009-06-27T14:49:50Z

2009-06-27T14:49:30Z

2009-06-27T14:42:43Z

2009-06-27T14:37:17Z

2009-06-27T14:36:03Z

2009-06-27T14:34:38Z

2009-06-27T14:03:40Z

2009-06-17T18:59:06Z

Key Investigators

2009-06-17T18:55:58Z

@@ Line 46: / Line 46: @@
 * Ongoing : EPI distortion correction under test
 ** Rician & EPI are cmake ready for python wrapping
-* Even if not perfect, wrapitk allows:
+* Even if not perfect, WrapITK allows:
 ** to build efficient VTK/ITK pipeline - with the python benefits
-** to integrate easily a C++ class developed in ITK/VTK up to setup a cmake configuration file
+** to integrate easily a C++ class developed in ITK/VTK: it is just up to write a small cmake configuration file
 ** >90% of ITK and VTK classes are usable at once
 ** quite cumbersome to understand why people argue against it ;-)

@@ Line 50: / Line 50: @@
 ** to integrate easily a C++ class developed in ITK/VTK up to setup a cmake configuration file
 ** >90% of ITK and VTK classes are usable at once
-** quite cumbersome to know why people argue against it ;-)
+** quite cumbersome to understand why people argue against it ;-)
 </div>

@@ Line 46: / Line 46: @@
 * Ongoing : EPI distortion correction under test
 ** Rician & EPI are cmake ready for python wrapping
 </div>

@@ Line 40: / Line 40: @@
 <h3>Progress</h3>
-* Achieved itk integration through WrapITK into the python pipeline
+* Achieved ITK integration through WrapITK into the python pipeline
 ** alternative under discussion for the Slicer side: weave seems to be a better candidate
 * Tested numpy conversion to/from VTK/ITK
 * Ongoing : EPI distortion correction under test
 </div>

@@ Line 41: / Line 41: @@
 <h3>Progress</h3>
 * Achieved itk integration through WrapITK into the python pipeline
-** alternative under discussion for the Slicer side: weave seems to be ideal
+** alternative under discussion for the Slicer side: weave seems to be a better candidate
 * Tested numpy conversion to/from VTK/ITK
 * Ongoing : EPI distortion correction under test

@@ Line 17: / Line 17: @@
 <h3>Objective</h3>
-To create an end-to-end analysis pipeline to study white matter anomalies using a stochastic tractography algorithm.
+To create an end-to-end analysis pipeline to study white matter anomalies using a stochastic tractography algorithm in VCFS population.
 See our [[DBP2:Harvard:Brain_Segmentation_Roadmap| Roadmap]] for more details.
@@ Line 33: / Line 33: @@
 * Eddy current correction
 </div>

@@ Line 1: / Line 1: @@
 __NOTOC__
 <gallery>
-Image:PW2009-v3.png|[[2009_Summer_Project_Week#Projects|Projects List]]
+Image:PW2009-v3.png|[[2009_Summer_Project_Week#Projects|Back to Projects List]]
-Image:Anna.png|Tracts through the corpus connecting 2 cortical regions defined by fMRI activation.
+Image:Anna.png|Tracts through the corpus connecting two cortical regions defined by fMRI activation.
-Image:Image5.jpeg|ACC to OFC connection
+Image:Image5.jpeg|Display of Anterior Cingulate Cortex (ACC) and Orbito-Frontal Cortex (OFC).
-Image:Image11.jpeg|ACC to OFC connection
+Image:Image11.jpeg|Population study on ACC to OFC connection using stochastic tractography showed significant FA reduction in schizophrenics.
-Image:01040-lh-all-3D-cropped.png|IFG to Occ connection
+Image:01040-lh-all-3D-cropped.png|stochastic tractography of IFG-STG (arcuate) and IFG-occipital (IOFF) connections.
-Image:FA IFG-Occ scatter.jpg
+Image:FA IFG-Occ scatter.jpg|Significant finding in left IFG-occipital connections suggests decreased integrity of fiber tracts involved in language processing in schizophrenia.
 </gallery>