2013 Project Week:MRIAblation - Revision history

Lchauvin: /* Key Investigators */

2013-01-11T14:21:07Z

Key Investigators

Lchauvin: /* Key Investigators */

2013-01-10T02:59:11Z

Key Investigators

Lchauvin at 02:58, 10 January 2013

2013-01-10T02:58:22Z

Lchauvin at 20:29, 7 January 2013

2013-01-07T20:29:16Z

Lchauvin: /* Key Investigators */

2013-01-07T20:28:52Z

Key Investigators

Lchauvin: /* Key Investigators */

2013-01-07T20:26:40Z

Key Investigators

Lchauvin at 20:25, 7 January 2013

2013-01-07T20:25:12Z

Lchauvin at 16:54, 7 January 2013

2013-01-07T16:54:29Z

Lchauvin at 16:54, 7 January 2013

2013-01-07T16:54:01Z

Noby at 16:14, 27 December 2012

2012-12-27T16:14:06Z

@@ Line 32: / Line 32: @@
 * Basics functionalities are implemented, but the module is not very flexible (cannot read raw siemens header information, e.g. image size, data type, etc...).
 * [[Media:TempImaging.wmv |Video]]
+* Added widget to define image properties (size, spacing, origin)
 </div>
 </div>

@@ Line 35: / Line 35: @@
 </div>
 </div>
 ==Delivery Mechanism==

@@ Line 6: / Line 6: @@
 ==Key Investigators==
-* BWH: Laurent Chauvin, Noby Hata, Hatsuho Mamata
+* BWH: Laurent Chauvin, Noby Hata, Hatsuho Mamata, Alex Golby
 <div style="margin: 20px;">

@@ Line 35: / Line 35: @@
 </div>
 </div>
 ==Delivery Mechanism==

@@ Line 7: / Line 7: @@
 ==Key Investigators==
 * BWH: Laurent Chauvin, Noby Hata, Hatsuho Mamata
 <div style="margin: 20px;">
@@ Line 19: / Line 18: @@
 <div style="width: 27%; float: left; padding-right: 3%;">
 <h3>Approach, Plan</h3>

@@ Line 31: / Line 31: @@
 <h3>Progress</h3>
 * Basics functionalities are implemented, but the module is not very flexible (cannot read raw siemens header information, e.g. image size, data type, etc...).
-* [[Media:TempImaging.wmv |Progress]]
+* [[Media:TempImaging.wmv |Video]]
 </div>

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

← Older revision		Revision as of 16:54, 7 January 2013
Line 40:		Line 40:

	*To investigator appropriate distribution mechanism. Extension manager? What is the expected level of quality? Who should I talk to ? Multi-OS support needed? What level of documentation is need. We are ready to distribute this module to open source community, but we are not familiar with the up-to-date distribution mechanism.		*To investigator appropriate distribution mechanism. Extension manager? What is the expected level of quality? Who should I talk to ? Multi-OS support needed? What level of documentation is need. We are ready to distribute this module to open source community, but we are not familiar with the up-to-date distribution mechanism.
−

	==References==		==References==

← Older revision		Revision as of 16:54, 7 January 2013
Line 1:		Line 1:
		+	__NOTOC__
		+	<gallery>
		+	Image:PW-SLC2013.png\|[[2013_Winter_Project_Week#Projects\|Projects List]]
		+	</gallery>
		+
		+	==Key Investigators==
		+	* BWH: Laurent Chauvin, Noby Hata, Hatsuho Mamata
		+
		+
		+	<div style="margin: 20px;">
		+	<div style="width: 27%; float: left; padding-right: 3%;">
		+
		+	<h3>Objective</h3>
		+	The goal is to automatically monitor tissues temperature (visually and graphically) using phase images during laser ablation intervention.
		+	Fiducials could also be placed to monitor temperature evolution at a specific location (tip of the probe, important structures, etc...)
		+
		+	</div>
		+
		+	<div style="width: 27%; float: left; padding-right: 3%;">
		+
		+	<h3>Approach, Plan</h3>
		+	* Read phase images
		+	* Compute thermal images
		+	* Display temperature evolution
		+
		+	</div>
		+
		+	<div style="width: 40%; float: left;">
		+
		+	<h3>Progress</h3>
		+	* Basics functionalities are implemented, but the module is not very flexible (cannot read raw siemens header information, e.g. image size, data type, etc...).
		+	* [[Media:TempImaging.wmv \|Progress]]
		+
		+	</div>
		+	</div>
		+
		+	==Delivery Mechanism==
		+
		+	This work will be a Slicer4 module, maybe extension.
		+
	*To investigator appropriate distribution mechanism. Extension manager? What is the expected level of quality? Who should I talk to ? Multi-OS support needed? What level of documentation is need. We are ready to distribute this module to open source community, but we are not familiar with the up-to-date distribution mechanism.		*To investigator appropriate distribution mechanism. Extension manager? What is the expected level of quality? Who should I talk to ? Multi-OS support needed? What level of documentation is need. We are ready to distribute this module to open source community, but we are not familiar with the up-to-date distribution mechanism.
		+
		+
		+	==References==

← Older revision		Revision as of 16:14, 27 December 2012
Line 1:		Line 1:
−	*To investigator appropriate distribution mechanism. Extension manager? What is the expected level of quality? Who should I talk to ? Multi-OS support?	+	*To investigator appropriate distribution mechanism. Extension manager? What is the expected level of quality? Who should I talk to ? Multi-OS support needed? What level of documentation is need. We are ready to distribute this module to open source community, but we are not familiar with the up-to-date distribution mechanism.