Difference between revisions of "ITK -VTK wrapper"

From NAMIC Wiki
Jump to: navigation, search
(Created page with '__NOTOC__ <gallery> Image:PW-MIT2013.png|Projects List </gallery> ==Key Investigators== * UNICZ: Paolo Zaffino * UIowa: Dave Welch, Hans Jo…')
 
 
(3 intermediate revisions by the same user not shown)
Line 2: Line 2:
 
<gallery>
 
<gallery>
 
Image:PW-MIT2013.png|[[2013_Summer_Project_Week#Projects|Projects List]]
 
Image:PW-MIT2013.png|[[2013_Summer_Project_Week#Projects|Projects List]]
 +
Image:Python commands.png
 
</gallery>
 
</gallery>
  
 
==Key Investigators==
 
==Key Investigators==
 
* UNICZ: Paolo Zaffino
 
* UNICZ: Paolo Zaffino
* UIowa: Dave Welch, Hans Johnson
+
* MGH: Greg Sharp
 +
* Isomics: Steve Pieper
  
 
<div style="margin: 20px;">
 
<div style="margin: 20px;">
Line 27: Line 29:
  
 
<h3>Progress</h3>
 
<h3>Progress</h3>
TBD.
+
The wrapper is almost ready.
 +
It can run registrations using Slicer node as images input and all the registration parameters can be setted from the Python command line.
 +
The last step is to get the registration result available in the current Slicer scene.
  
  
 
</div>
 
</div>
 
</div>
 
</div>

Latest revision as of 12:40, 21 June 2013

Home < ITK -VTK wrapper

Key Investigators

  • UNICZ: Paolo Zaffino
  • MGH: Greg Sharp
  • Isomics: Steve Pieper

Objective

We want to implement an ITK - VTK wrapper in order to make possible to call ITK functions from the embedded Python in Slicer. In particular we want to run a Plastimatch registration from a Python script executed by the built-in interpreter.

Approach, Plan

Write C++ code in order to wrap the ITK layer.

Progress

The wrapper is almost ready. It can run registrations using Slicer node as images input and all the registration parameters can be setted from the Python command line. The last step is to get the registration result available in the current Slicer scene.