2009 Summer Project Week 4D Imaging discussion - Revision history

Tokuda: /* Minutes */

2009-06-26T13:24:22Z

Minutes

Tokuda: /* Minutes */

2009-06-26T13:23:23Z

Minutes

Tokuda: /* Minutes */

2009-06-26T13:21:52Z

Minutes

Tokuda: /* Minutes */

2009-06-26T13:14:57Z

Minutes

Tokuda at 13:05, 26 June 2009

2009-06-26T13:05:42Z

Tokuda: /* Agenda */

2009-06-23T12:36:11Z

Agenda

Tokuda: /* Agenda */

2009-06-23T12:35:22Z

Agenda

Tokuda at 21:10, 22 June 2009

2009-06-22T21:10:52Z

Tokuda: Created page with '=Meeting: 4D image for 3D Slicer= ==Time & Place== 8:30am - , June 23, 2009 MIT. Grier Rooms A & B: 34-401A & 34-401B. ==Attendees== ==Agenda== *Demo of the prototype of 4D ...'

2009-06-22T21:08:12Z

Created page with '=Meeting: 4D image for 3D Slicer= ==Time & Place== *8:30am - , June 23, 2009 *MIT. Grier Rooms A & B: 34-401A & 34-401B. ==Attendees== ==Agenda== *Demo of the prototype of 4D ...'

New page

=Meeting: 4D image for 3D Slicer=

==Time & Place==
*8:30am - , June 23, 2009
*MIT. Grier Rooms A & B: 34-401A & 34-401B.

==Attendees==

==Agenda==
*Demo of the prototype of 4D Image Module in 3D Slicer
*Possible applications, requirements,
*Review the current implementation 4D Bundle: vtkMRML4DBundleNode class
*GUI design

← Older revision		Revision as of 13:24, 26 June 2009
Line 48:		Line 48:
	<br>		<br>

		+	Go to [[2009_Summer_Project_Week_4D_Imaging]]
	Go to [[2009_Summer_Project_Week]]		Go to [[2009_Summer_Project_Week]]

@@ Line 33: / Line 33: @@
 *Danielle’s Cardiac application.
 *In ITK, time series database has been implemented. We should evaluate how these two strategies compare with each other.
 *Caching may be good.
 *Check volume rendering with 4D images. It is a good application to use CUDA.

@@ Line 43: / Line 43: @@
 *Scalar color maps should be integrated with the 4D module and should be corresponded to look up tables. This is especially useful for nuclear medicine.
 *Is it possible to load and manipulate two different fourD bundles simultaneously?
+*Hide volume from Data module?
 <br>
 Go to [[2009_Summer_Project_Week]]

@@ Line 23: / Line 23: @@
 ==Minutes==
-(Jayender kindly took this minutes. Thanks!)
+(Based on Jayender's minutes. Thanks, Jay!)
-#Junichi introduced 4D imaging and analysis for lung perfusion.
+*Junichi introduced 4D imaging and analysis for lung perfusion.
-#Ron suggested to develop another module for preparing the nrrhd file from dicom images since this is input to the 4D module. The user should find it easy to input the images to the module.
+*Ron suggested to develop another module for preparing the nrrhd file from dicom images since this is input to the 4D module. The user should find it easy to input the images to the module.
-#Control GUI for interacting with the module could be added outside the main Slicer GUI.
+*Control GUI for interacting with the module could be added outside the main Slicer GUI.
-#For the analysis, a color coding scheme should be introduced to identify the curves being analyzed.
+*For the analysis, a color coding scheme / label name should be introduced to identify the curves being analyzed.
-#It was common consensus that this implementation of the 4D module is the best since it is the only one available in Slicer!
+*It was common consensus that this implementation of the 4D module is the best since it is the only one available in Slicer!
-#DCE is an emerging capability. Therefore it is important that the module should be capable of handing this scenario.
+*DCE is an emerging capability. Therefore it is important that the module should be capable of handing this scenario.
-#fMRI is another possible application for the module – Danielle’s application.
+*fMRI is another possible application for the module
-#In ITK, time series database has been implemented. We should evaluate how these two strategies compare with each other.
+*Danielle’s Cardiac application.
-#Caching may be good.
+*In ITK, time series database has been implemented. We should evaluate how these two strategies compare with each other.
-#Check volume rendering with 4D images. It is a good application to use CUDA.
+*Caching may be good.
-#4D image registration is very useful and should be worked on. Batchmake is also quite useful.
+*Check volume rendering with 4D images. It is a good application to use CUDA.
-#Evaluate how the 4D module integrates with the change tracker.
+*4D image registration is very useful and should be worked on. Batchmake is also quite useful.
-#Irregular time stamps for the data should also be included in the 4D data. This would be useful to evaluate the growth or recession of a tumor over time. Explicit time stamping is required.
-#It should also be possible to perform parameter calculation based on the actual time stamp. This will enhance the analysis aspect of the module.
+*Evaluate how the 4D module integrates with the change tracker.
-#It will also be useful to develop a bidirectional map between the image and parameter space. How does a parameter influence the image as well as parameter evaluation from the images.
+*Irregular time stamps for the data should also be included in the 4D data. This would be useful to evaluate the growth or recession of a tumor over time. Explicit time stamping is required.
-#Scalar color maps should be integrated with the 4D module and should be corresponded to look up tables. This is especially useful for nuclear medicine.
+*It should also be possible to perform parameter calculation based on the actual time stamp. This will enhance the analysis aspect of the module.
-#Is it possible to load and manipulate two different fourD bundles simultaneously?
+*It will also be useful to develop a bidirectional map between the image and parameter space. How does a parameter influence the image as well as parameter evaluation from the images.

← Older revision		Revision as of 13:05, 26 June 2009
Line 22:		Line 22:
	*GUI design		*GUI design

		+	==Minutes==
		+	(Jayender kindly took this minutes. Thanks!)
		+	#Junichi introduced 4D imaging and analysis for lung perfusion.
		+	#Ron suggested to develop another module for preparing the nrrhd file from dicom images since this is input to the 4D module. The user should find it easy to input the images to the module.
		+	#Control GUI for interacting with the module could be added outside the main Slicer GUI.
		+	#For the analysis, a color coding scheme should be introduced to identify the curves being analyzed.
		+	#It was common consensus that this implementation of the 4D module is the best since it is the only one available in Slicer!
		+	#DCE is an emerging capability. Therefore it is important that the module should be capable of handing this scenario.
		+	#fMRI is another possible application for the module – Danielle’s application.
		+	#In ITK, time series database has been implemented. We should evaluate how these two strategies compare with each other.
		+	#Caching may be good.
		+	#Check volume rendering with 4D images. It is a good application to use CUDA.
		+	#4D image registration is very useful and should be worked on. Batchmake is also quite useful.
		+	#Evaluate how the 4D module integrates with the change tracker.
		+	#Irregular time stamps for the data should also be included in the 4D data. This would be useful to evaluate the growth or recession of a tumor over time. Explicit time stamping is required.
		+	#It should also be possible to perform parameter calculation based on the actual time stamp. This will enhance the analysis aspect of the module.
		+	#It will also be useful to develop a bidirectional map between the image and parameter space. How does a parameter influence the image as well as parameter evaluation from the images.
		+	#Scalar color maps should be integrated with the 4D module and should be corresponded to look up tables. This is especially useful for nuclear medicine.
		+	#Is it possible to load and manipulate two different fourD bundles simultaneously?

@@ Line 16: / Line 16: @@
 ***pointers to display0 and display1 volume nodes
 ***Copies image arrays from volume frames to display0 / display1 to scroll in time-dimension
 *GUI design

@@ Line 10: / Line 10: @@
 *Demo of the prototype of 4D Image Module in 3D Slicer
 *Possible applications, requirements,
-*Review the current implementation 4D Bundle: vtkMRML4DBundleNode class
+*Review the current implementation
 *GUI design

← Older revision		Revision as of 21:10, 22 June 2009
Line 12:		Line 12:
	*Review the current implementation 4D Bundle: vtkMRML4DBundleNode class		*Review the current implementation 4D Bundle: vtkMRML4DBundleNode class
	*GUI design		*GUI design
		+
		+
		+
		+	<br>
		+
		+	Go to [[2009_Summer_Project_Week]]

2009 Summer Project Week 4D Imaging discussion - Revision history

Tokuda: /* Minutes */

Tokuda: /* Minutes */

Tokuda: /* Minutes */

Tokuda: /* Minutes */

Tokuda at 13:05, 26 June 2009

Tokuda: /* Agenda */

Tokuda: /* Agenda */

Tokuda at 21:10, 22 June 2009

Tokuda: Created page with '=Meeting: 4D image for 3D Slicer= ==Time & Place== *8:30am - , June 23, 2009 *MIT. Grier Rooms A & B: 34-401A & 34-401B. ==Attendees== ==Agenda== *Demo of the prototype of 4D ...'

Tokuda: Created page with '=Meeting: 4D image for 3D Slicer= ==Time & Place== 8:30am - , June 23, 2009 MIT. Grier Rooms A & B: 34-401A & 34-401B. ==Attendees== ==Agenda== *Demo of the prototype of 4D ...'