Difference between revisions of "2013 Project Week:MRIAblation"

From NAMIC Wiki
Jump to: navigation, search
 
(4 intermediate revisions by the same user not shown)
Line 6: Line 6:
  
 
==Key Investigators==
 
==Key Investigators==
* BWH: Laurent Chauvin, Noby Hata, Hatsuho Mamata
+
* BWH: Laurent Chauvin, Noby Hata, Hatsuho Mamata, Alex Golby
 
 
  
 
<div style="margin: 20px;">
 
<div style="margin: 20px;">
Line 19: Line 18:
  
 
<div style="width: 27%; float: left; padding-right: 3%;">
 
<div style="width: 27%; float: left; padding-right: 3%;">
 +
  
 
<h3>Approach, Plan</h3>
 
<h3>Approach, Plan</h3>
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...).
 
* 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]]
 
* [[Media:TempImaging.wmv |Video]]
 
+
* Added widget to define image properties (size, spacing, origin)
 
</div>
 
</div>
 
</div>
 
</div>

Latest revision as of 14:21, 11 January 2013

Home < 2013 Project Week:MRIAblation

Key Investigators

  • BWH: Laurent Chauvin, Noby Hata, Hatsuho Mamata, Alex Golby

Objective

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...)


Approach, Plan

  • Read phase images
  • Compute thermal images
  • Display temperature evolution

Progress

  • Basics functionalities are implemented, but the module is not very flexible (cannot read raw siemens header information, e.g. image size, data type, etc...).
  • Video
  • Added widget to define image properties (size, spacing, origin)

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.

References