2012 Project Week:4DImageSlicer4 - Revision history

Fedorov: /* Key Investigators */

2012-02-20T18:54:48Z

Key Investigators

2012-01-13T16:39:56Z

2012-01-13T16:37:19Z

Key Investigators

2012-01-13T16:37:00Z

Key Investigators

2012-01-13T15:58:56Z

2012-01-09T23:17:01Z

Key Investigators

2012-01-09T23:15:16Z

2012-01-09T23:03:37Z

2012-01-07T16:01:57Z

Key Investigators

2012-01-04T16:24:03Z

Key Investigators

← Older revision		Revision as of 18:54, 20 February 2012
Line 51:		Line 51:

	Jim is in the final stages of integrating new charting capabilities into Slicer4 trunk, we are ready to use them in this project as soon as they are available.		Jim is in the final stages of integrating new charting capabilities into Slicer4 trunk, we are ready to use them in this project as soon as they are available.
		+
		+	'''Progress since project week''': modules renamed, planned for inclusion in Slicer 4.1:
		+	* https://github.com/fedorov/MultiVolumeImporter
		+	* https://github.com/fedorov/MultiVolumeExplorer

	</div>		</div>

@@ Line 2: / Line 2: @@
 <gallery>
 Image:PW-SLC2011.png|[[2011_Winter_Project_Week#Projects|Projects List]]
 </gallery>

← Older revision		Revision as of 16:37, 13 January 2012
Line 50:		Line 50:

	Jim is in the final stages of integrating new charting capabilities into Slicer4 trunk, we are ready to use them in this project as soon as they are available.		Jim is in the final stages of integrating new charting capabilities into Slicer4 trunk, we are ready to use them in this project as soon as they are available.
−
−	~~Questions:~~
−	* are VTK plotting capabilities as in RT module available from python
−	** ctkVTKChartView is not accessible fully from python, need to wrap, or use Jim's solution
−	** a ChartViewer (like a SliceView or 3D View that can be packed in a layout) is under development - Jim
−	* python vs c++ for the DCE GUI module
−	** C++ with delegation of GUI management to Python was chosen for implementation

	</div>		</div>

@@ Line 11: / Line 11: @@
 * GE: Emma Zhu
 * GE: Jim Miller
 <div style="margin: 20px;">
@@ Line 46: / Line 47: @@
 # '''VectorImageExplorer''': C++/Python module to support user interaction with VectorImageContainer: scroll in the fourth dimension, probe data at a selected location, plotting of the curves (implementation in progress available on github:  [https://github.com/fedorov/VectorImageExplorer VectorImageExplorer]. As of now, this module allows to scroll in fourth dimension, probe data and display vector as a string in the module GUI. Next step is to add plotting.
 Questions:

@@ Line 38: / Line 38: @@
 <h3>Progress</h3>
-Initial experiments showed the feasibility of the proposed approach:
+The design of the module has been discussed, implementation is underway.
-* DicomToNrrdConverer works for DCE data
-* B-values field can be used to store timestamps
+We introduced a new MRML node named "VectorImageContainer" to encapsulate DWI node and provide generic functionality for operating 3D+1 images. This module can be used not only for time series visualization (3D+t), but in other applications (e.g., T1 and T2 estimation: 3D+RepetitionTime, 3D+FlipAngle). The node will also contain metadata to identify the type of the information stored in the vectors, and the labels for each element.
 Questions:
 * are VTK plotting capabilities as in RT module available from python
 ** a ChartViewer (like a SliceView or 3D View that can be packed in a layout) is under development - Jim
 * python vs c++ for the DCE GUI module
-* DWI volume has B-values vector, but only the last B-value is saved in the NRRD volume by Slicer -- is this expected?
+** C++ with delegation of GUI management to Python was chosen for implementation
 </div>
@@ Line 56: / Line 61: @@
 ==Delivery Mechanism==
-This work will be delivered to the NA-MIC Kit as a combination of core functionality and customized modules of 3D Slicer v.4
+This work will be delivered to the NA-MIC Kit as a Slicer4 extension.
 ==Meeting notes==

@@ Line 25: / Line 25: @@
 <h3>Approach, Plan</h3>
+Discuss the architecture and implementation approach, specifically should address:
 </div>

@@ Line 26: / Line 26: @@
 <h3>Approach, Plan</h3>
 </div>
@@ Line 81: / Line 53: @@
 This work will be delivered to the NA-MIC Kit as a core functionality of 3D Slicer v.4
 ==References==

@@ Line 30: / Line 30: @@
 Considering input from Steve, the ambitions were down-scaled.
-An alternative approach could be:
+Approaches to consider:
 * use DicomToNrrdConverter to make a fake DWI from a DCE series
 * use custom module to inject timestamps into the DWI volume node, as if these were B-values. This way we can store timestamps together with the data.
@@ Line 37: / Line 37: @@
 ** plotting area for visualizing time curves
 ** support for interactive selection of spatial location using mouse/keyboard or fiducial
+* Port the 4D Image and Analysis modules from Slicer3

@@ Line 9: / Line 9: @@
 * BWH: Junichi Tokuda
 * MGH: Jayashree Kalpathy-Cramer
 <div style="margin: 20px;">