Difference between revisions of "Slicer3:Prostate Intervention Module"

From NAMIC Wiki
Jump to: navigation, search
Line 2: Line 2:
 
*Provide step-by-step navigation for prostate intervention.
 
*Provide step-by-step navigation for prostate intervention.
 
*Integrate two existing modules [http://www.slicer.org/slicerWiki/index.php/Modules:ProstateNav-Documentation-3.4 ProstateNav] and [http://svn.na-mic.org/NAMICSandBox/trunk/Queens/TRProstateBiopsy/ Queen's Transrectal Prostate Biopsy Module].
 
*Integrate two existing modules [http://www.slicer.org/slicerWiki/index.php/Modules:ProstateNav-Documentation-3.4 ProstateNav] and [http://svn.na-mic.org/NAMICSandBox/trunk/Queens/TRProstateBiopsy/ Queen's Transrectal Prostate Biopsy Module].
 +
 +
=Task List=
 +
==Haiying's task list (Created on 4/29/2010)==
 +
*Get familiar with the module.
 +
**Go through the tutorial in [http://www.slicer.org/slicerWiki/index.php/Modules:ProstateNav-Documentation-3.6 ProstateNav Documentation].
 +
*Minor changes:
 +
**Template
 +
***We don't need the workspace model
 +
***Change the name of buttons in the Targeting page. '''Move''' should be '''Select hole'''. We don't need '''Stop button'''.
 +
**Transperineal Robot
 +
 +
  
 
=Discussions=
 
=Discussions=
 +
==6/16/2009==
 
*Which module could we take as a basis for the development?
 
*Which module could we take as a basis for the development?
 
**ProstateNav (it is already in the trunk, supports OpenIGTLink)
 
**ProstateNav (it is already in the trunk, supports OpenIGTLink)

Revision as of 18:34, 29 April 2010

Home < Slicer3:Prostate Intervention Module

Objective

Task List

Haiying's task list (Created on 4/29/2010)

  • Get familiar with the module.
  • Minor changes:
    • Template
      • We don't need the workspace model
      • Change the name of buttons in the Targeting page. Move should be Select hole. We don't need Stop button.
    • Transperineal Robot


Discussions

6/16/2009

  • Which module could we take as a basis for the development?
    • ProstateNav (it is already in the trunk, supports OpenIGTLink)
    • Junichi will strip down the code.
  • Workflow wizard steps
    • Should be specialized / customized for different applications
    • Two approaches for configurable wizard:
      • Static: The workflow is defined when the developer builds 3D Slicer
      • Dynamic: Run-time configuration. The users can configure the workflow by:
        • Choosing from the list of the pages in the GUI
        • Load XML file.
  • Supporting different devices
    • Use OpenIGTLink as an abstraction layer


People

  • Andras Lasso, Queen's University
  • Junichi Tokuda, Brigham and Women's Hospital