Difference between revisions of "2013 Project Week Breakout Session:Slicer4Python"
(→Goals) |
(→Topics) |
||
Line 6: | Line 6: | ||
=Topics= | =Topics= | ||
− | ==Creating module from | + | ==Creating a scripted module from templates with ModuleWizard== |
+ | This topic is covered in [[Documentation/Nightly/Developers/ModuleWizard | the ModuleWizard documentation]]. It allows you to create a skeleton extension with any combination of modules you want. | ||
+ | |||
+ | |||
== Configuring slicer to use the module== | == Configuring slicer to use the module== | ||
== Basic Development Cycle== | == Basic Development Cycle== | ||
Line 13: | Line 16: | ||
== Refine functionality == | == Refine functionality == | ||
== Document == | == Document == | ||
+ | |||
= Package as extension = | = Package as extension = | ||
= The hard parts = | = The hard parts = |
Revision as of 15:54, 12 June 2013
Home < 2013 Project Week Breakout Session:Slicer4PythonBack to Summer project week Agenda
Goals
The material here provides a guided walk through of the resources available for python scripting in Slicer 4. It is based on what is available in the nightly builds as of project week (June 17, 2013). One goal is to demonstrate the development of a python scripted slicer module. Another goal is to provide "A Guide to Python in Slicer for the Casual Power User" which means that this walkthrough of the features of slicer should give you an idea how to make a custom module that helps organize and automate your processing. This can be useful for your own research or you can create helper modules that simplify the work for users who are exploring an algorithm or working with a large set of studies.
Topics
Creating a scripted module from templates with ModuleWizard
This topic is covered in the ModuleWizard documentation. It allows you to create a skeleton extension with any combination of modules you want.