Difference between revisions of "2008 Summer Project Week:PythonInSlicer"
(New page: {| |thumb|320px|Return to [[2008_Summer_Project_Week|Project Week Main Page ]] |thumb|320px|[http://www.python.org] |} __NOTOC__...) |
|||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 12: | Line 12: | ||
* Dan Blezek | * Dan Blezek | ||
* Mike Halle | * Mike Halle | ||
| − | * Steve | + | * Steve Pieper |
* Demian Wasserman | * Demian Wasserman | ||
| Line 22: | Line 22: | ||
To finalize the use of Python within Slicer for command-line modules, scripted modules and meta-modules (or module chaining). The main rework is needed for scripted modules. | To finalize the use of Python within Slicer for command-line modules, scripted modules and meta-modules (or module chaining). The main rework is needed for scripted modules. | ||
| + | We will discuss what would be needed to create a Scripted Module tutorial using python. | ||
</div> | </div> | ||
| Line 35: | Line 36: | ||
During the January 2008 project week, within [[Projects/Slicer3/2007_Project_Week_Python support in Slicer3|Python Support in Slicer 3]], preliminary Python support for Numpy/Scipy, command line modules (executed in the main thread), calling of all registered modules from Python and scripted modules have been added. | During the January 2008 project week, within [[Projects/Slicer3/2007_Project_Week_Python support in Slicer3|Python Support in Slicer 3]], preliminary Python support for Numpy/Scipy, command line modules (executed in the main thread), calling of all registered modules from Python and scripted modules have been added. | ||
| + | |||
| + | In June 2008 significant progress was made to clean up the implementation to make the python code behave identically to python-wrapped VTK code and minimize the any special cases that python developers need to keep in mind when writing slicer code. Some cleanup work is required for shutdown to avoid leaks/crashes. | ||
| + | |||
| + | Next step is to enable python by default in the slicer3 trunk builds and then develop a tutorial for writing a python-based scripted module at future courses. | ||
| + | |||
</div> | </div> | ||
| Line 43: | Line 49: | ||
===References=== | ===References=== | ||
| − | * [http://www.python.org] | + | * [http://www.python.org www.python.org] |
Latest revision as of 12:52, 27 June 2008
Home < 2008 Summer Project Week:PythonInSlicer Return to Project Week Main Page |
Key Investigators
- Luca Antiga
- Dan Blezek
- Mike Halle
- Steve Pieper
- Demian Wasserman
Objective
To finalize the use of Python within Slicer for command-line modules, scripted modules and meta-modules (or module chaining). The main rework is needed for scripted modules.
We will discuss what would be needed to create a Scripted Module tutorial using python.
Approach, Plan
The plan for the project week is to get the status of Python within Slicer ready for release. This will involve some general code review and some rework on Python Scripted Module infrastructure.
Progress
During the January 2008 project week, within Python Support in Slicer 3, preliminary Python support for Numpy/Scipy, command line modules (executed in the main thread), calling of all registered modules from Python and scripted modules have been added.
In June 2008 significant progress was made to clean up the implementation to make the python code behave identically to python-wrapped VTK code and minimize the any special cases that python developers need to keep in mind when writing slicer code. Some cleanup work is required for shutdown to avoid leaks/crashes.
Next step is to enable python by default in the slicer3 trunk builds and then develop a tutorial for writing a python-based scripted module at future courses.
