Difference between revisions of "2013 Project Week Breakout Session:Slicer4Python"

From NAMIC Wiki
Jump to: navigation, search
Line 3: Line 3:
 
=Goals=
 
=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.
+
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=
 
=Topics=

Revision as of 16:26, 12 June 2013

Home < 2013 Project Week Breakout Session:Slicer4Python
Back 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.

Prerequisites

We'll go through the steps on a Mac, but the steps are essentially the same on all platforms. We'll be using a locally built version of slicer created using these instructions, but the steps can also be performed using a binary download as long as you have a checkout of the slicer source code available.

Make an extension framework

For this example we'll make an extension with a single scripted module as a demonstration. We run the following command from the Slicer source directory.

./Utilities/Scripts/ModuleWizard.py --template ./Extensions/Testing/ScriptedLoadableExtensionTemplate --target ../VolumeTools VolumeTools

We call the extension "VolumeTools" because we will use it to host a demonstration scripted module that scrolls through the volumes available in the current scene.

Configuring slicer to use the module

Basic Development Cycle

Edit / Reload the code

Develop self-tests

Refine functionality

Document

Package as extension

The hard parts

building the GUI

finding the right slicer class/calls to implement what you want

debugging

optimizing performance

Special Topics

The slicer architecture

the qSlicerApplication

the vtkSlicerApplicationLogic

the vtkMRMLScene

slicer.modules

slicer.util

Manipulating the slicer session via python

Working with python modules that are not bundled with slicer's binary distribution