Difference between revisions of "2009 Winter Project Week Python"
| Line 36: | Line 36: | ||
- review the Slicer Python to Numpy code and eventually extend it to handle more general image or data types | - review the Slicer Python to Numpy code and eventually extend it to handle more general image or data types | ||
| + | |||
| + | - implement callback functions in Slicer Python, for widgets and programmable filters | ||
As for packaging problems, testing will have to be performed on several architectures. | As for packaging problems, testing will have to be performed on several architectures. | ||
Revision as of 12:26, 12 December 2008
Home < 2009 Winter Project Week Python
Key Investigators
- Luca Antiga (Medical Imaging Unit, Biomedical Engineering Department, Mario Negri Institute)
- Steve Piper (Isomics)
- Demian Wasserman (INRIA)
Objective
To finalize the implementation of the Slicer Python interface and solve packaging problems linked to Scipy.
Approach, Plan
The Slicer Python interface now works well for both non-interactive and interactive modules. A few improvements are still needed, namely
- calling VTK static methods - e.g. slicer.vtkMath.Norm(v)
- handling modified arguments - e.g. slicer.vtkMath::Normalize(v)
- defining methods with the exact number of arguments (now it's not constrained, so if it's wrong Tcl complains) - this will require a patch on the VTK Tcl wrappers
- fix a memory leak associated with Python scripted modules
- review the Slicer Python to Numpy code and eventually extend it to handle more general image or data types
- implement callback functions in Slicer Python, for widgets and programmable filters
As for packaging problems, testing will have to be performed on several architectures.
Finally, documentation will be improved.
Progress
TODO
