Difference between revisions of "2009 Winter Project Week Slicer VMTK"
(Project Week Update) |
|||
Line 39: | Line 39: | ||
<h1>Progress</h1> | <h1>Progress</h1> | ||
− | An interactive python module skeleton has been created. Through a workaround the VMTK classes are already accessible in Slicer. Since now techniques like observers and callbacks are available in Slicer-Python the connection of the GUI and the algorithms should be ready soon. | + | An interactive python module<br> |
+ | skeleton has been created. Through<br> | ||
+ | a workaround the VMTK classes are<br> | ||
+ | already accessible in Slicer. Since<br> | ||
+ | now techniques like observers and<br> | ||
+ | callbacks are available in Slicer-Python<br> | ||
+ | the connection of the GUI and the<br> | ||
+ | algorithms should be ready soon. | ||
</div> | </div> |
Revision as of 20:15, 8 January 2009
Home < 2009 Winter Project Week Slicer VMTK
Key Investigators
- Daniel Haehn (Student of Medical Informatics, University of Heidelberg)
- Luca Antiga (Medical Imaging Unit, Biomedical Engineering Department, Mario Negri Institute)
- Ron
Objective
The Vascular Modeling Toolkit (VMTK) is a collection of libraries and tools for 3D reconstruction, geometric analysis, mesh generation and surface data analysis for image-based modeling of blood vessels. It should be very interesting to offer such techniques in Slicer3.
Approach, Plan
VMTK provides Python pipeable scripts (PypeS) to connect various commands and/or scripts. An automated mechanism to generate non-interactive Slicer modules has already been implemented.
The plan is to write a python scripted module for Slicer3 that connects to VMTK pipes and provides the same user interaction style found in VMTK. This is necessary for interactive segmentation.
In addition, a collection of non-interactive modules relevant to segmentation and characterization of vascular networks will be generated.
Finally, Slicer-vmtk packaging issues will be tackled.
Progress
An interactive python module
skeleton has been created. Through
a workaround the VMTK classes are
already accessible in Slicer. Since
now techniques like observers and
callbacks are available in Slicer-Python
the connection of the GUI and the
algorithms should be ready soon.