Difference between revisions of "Summer2009:Using ITK in python"
From NAMIC Wiki
| Line 1: | Line 1: | ||
__NOTOC__ | __NOTOC__ | ||
<gallery> | <gallery> | ||
| − | Image:PW2009-v3.png|[[2009_Summer_Project_Week|Project Week Main Page]] | + | Image:PW2009-v3.png|[[2009_Summer_Project_Week#Projects|Project Week Main Page]] |
Image:Itk75.png|ITK provides body of algorithms in C++ | Image:Itk75.png|ITK provides body of algorithms in C++ | ||
Image:Python-logo.gif|Python provides interactive development environment. | Image:Python-logo.gif|Python provides interactive development environment. | ||
Revision as of 02:39, 22 June 2009
Home < Summer2009:Using ITK in python
ITK provides body of algorithms in C++
Python provides interactive development environment.
Key Investigators
- GE: Jim Miller
- Isomics: Steve Pieper
- INRIA: Demian Wassermann
Objective
Develop strategies for embedding ITK filters in python code. See if this would be a workable strategy for creating slicer modules.
Approach, Plan
- Look at how numpy arrays are passed to C/C++ code using techniques like cython, weave, etc.
- Figure out what is needed to compile ITK code in these environments.
- Compare and contrast this approach to WrapITK
Progress
- Some pre-project week progress is shown on this page in the slicer.org wiki
