Difference between revisions of "2013 Summer Project Week Breakout Session:SlicerExtensions"

From NAMIC Wiki
Jump to: navigation, search
m
m
Line 10: Line 10:
 
== Goal ==
 
== Goal ==
  
−
During the breakout session we will walk through the resources available for creating extension in Slicer 4. It is based on a build of Slicer r22100 as of project week (June 17, 2013).
+
During the breakout session we will walk through the resources available for creating, building and distributing extension in Slicer 4. It is based on a build of Slicer r22100 and the wiki documentation as of project week (June 17, 2013).
  
−
One goal is to demonstrate the development and testing of a python scripted Slicer module.
+
Then we'll go through the list of Questions reported below and look at how the current system could be improved.
−
 
 
−
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.
 
−
 
 
−
In this tutorial, we'll make a module that allows you to quickly sequence through a set of volumes. We'll see how to make a custom GUI with a slider, how to implement the volume switching functionality, and how to write a self-test for the module.
 
−
Then we'll step back and look at how you could build on what you have learned in order to implement custom solutions to your research problems using Slicer's python interface.
 
  
  
Line 34: Line 29:
 
: Dashboard: shared between Slicer core and extensions (extensions appear in
 
: Dashboard: shared between Slicer core and extensions (extensions appear in
 
a different category)
 
a different category)
 +
  
 
* Process: Can you make a python scripted extension without a built version of slicer ?
 
* Process: Can you make a python scripted extension without a built version of slicer ?

Revision as of 19:23, 13 June 2013

Home < 2013 Summer Project Week Breakout Session:SlicerExtensions
Back to Summer project week Agenda

Before the breakout session


Goal

During the breakout session we will walk through the resources available for creating, building and distributing extension in Slicer 4. It is based on a build of Slicer r22100 and the wiki documentation as of project week (June 17, 2013).

Then we'll go through the list of Questions reported below and look at how the current system could be improved.


Q&A

Do not hesitate to edit this page and add more questions

  • Infrastructure: How much of slicer's core infrastructure should be used by extensions ?

From Andra Lasso: Currently the picture is quite mixed:

Source control: separate for all extensions
Issue tracking: separate for most extensions
Module documentation: shared between Slicer core and extensions

(extensions appear in a different section)

Hosting of binary releases: shared between Slicer core and extensions

(extensions appear in a different category)

Dashboard: shared between Slicer core and extensions (extensions appear in

a different category)


  • Process: Can you make a python scripted extension without a built version of slicer ?
Retrieved from "https://www.na-mic.org/w/index.php?title=2013_Summer_Project_Week_Breakout_Session:SlicerExtensions&oldid=81671"