Difference between revisions of "2009 Summer Project Week Liver Ablation Slicer"

From NAMIC Wiki
Jump to: navigation, search
Line 12: Line 12:
  
 
<h3>Objective</h3>
 
<h3>Objective</h3>
A complete workflow. This means loading the data, manually marking regions, processing this segmentation and exporting the result to the optimization program. After this we need to load the results of the optimization program and navigate.  
+
Implement a complete workflow:
 +
#Load data.
 +
#Manually mark regions (tumor, entry, critical structure).
 +
#Process segmentation and export information to planning module (executable plugin with command line options).  
 +
#Load results of the optimization program.
 +
#Configure OpenIGTLink module on Slicer and run OpenIGTLink IGSTK client.
 +
#Navigate.  
 
</div>
 
</div>
  
Line 18: Line 24:
  
 
<h3>Approach, Plan</h3>
 
<h3>Approach, Plan</h3>
Our plan for the project week is to integrate code from both sides and first try out.
+
#Integrate code from Georgetown for step 3 into Slicer.
 +
#Decide on appropriate format for describing the output of the optimization (set of trajectories and ablations along each trajectory).
 +
#Implement a stub executable plugin as a stand in for the optimization program.
 +
#Test the integrated workflow.
 
</div>
 
</div>
  

Revision as of 15:15, 11 June 2009

Home < 2009 Summer Project Week Liver Ablation Slicer

Key Investigators

  • BWH: Haiying Liu, Noby Hata
  • Georgetown: Ziv Yaniv

Objective

Implement a complete workflow:

  1. Load data.
  2. Manually mark regions (tumor, entry, critical structure).
  3. Process segmentation and export information to planning module (executable plugin with command line options).
  4. Load results of the optimization program.
  5. Configure OpenIGTLink module on Slicer and run OpenIGTLink IGSTK client.
  6. Navigate.

Approach, Plan

  1. Integrate code from Georgetown for step 3 into Slicer.
  2. Decide on appropriate format for describing the output of the optimization (set of trajectories and ablations along each trajectory).
  3. Implement a stub executable plugin as a stand in for the optimization program.
  4. Test the integrated workflow.

Progress

A new module is being created in Slicer3.