Difference between revisions of "2015 Summer Project Week:IGTSliceletBase"

From NAMIC Wiki
Jump to: navigation, search
 
(13 intermediate revisions by the same user not shown)
Line 4: Line 4:
 
Image:FullScreenModule02.png|Full-screen module example 1
 
Image:FullScreenModule02.png|Full-screen module example 1
 
Image:FullScreenModule01.png|Full-screen module example 2
 
Image:FullScreenModule01.png|Full-screen module example 2
Image:FullScreenModule03.png|Full-screen module example 3
+
Image:LumpNav-Touchscreen.png|3D Slicer used in the operating room for breast surgery guidance
 
</gallery>
 
</gallery>
  
Line 18: Line 18:
 
<div style="width: 27%; float: left; padding-right: 3%;">
 
<div style="width: 27%; float: left; padding-right: 3%;">
 
<h3>Objective</h3>
 
<h3>Objective</h3>
* Create base classes and utility functions for quick implementation of slicelets that are convenient to use in the operating room
+
* Generalize current Slicer-based intra-operative/surgical applications that are already successfully translated to the operating room
 +
* Create base classes and utility functions for easy implementation of slicelets/full-screen modules that are convenient to use in the operating room, running on tablets and laptops
 
</div>
 
</div>
 
<div style="width: 27%; float: left; padding-right: 3%;">
 
<div style="width: 27%; float: left; padding-right: 3%;">
 
<h3>Approach, Plan</h3>
 
<h3>Approach, Plan</h3>
 
* Questions:
 
* Questions:
** What are the required features?
+
** Slicelet/full-screen module, docking widgets (slicelets seem to have performance issue and it's difficult to make sure nothing relies on main window, status bar, etc.)  
*** Save/load scene
 
*** Record procedure
 
*** Switch between simplified/full slicer GUI
 
*** ...?
 
** Slicelet/full-screen module (slicelets seem to have performance issue and it's difficult to make sure nothing relies on main window, status bar, etc.)  
 
 
** Scene initialization: create empty scene/activate loaded scene
 
** Scene initialization: create empty scene/activate loaded scene
 
** How to split code to multiple files but still allow reloading (similarly to Editor?)
 
** How to split code to multiple files but still allow reloading (similarly to Editor?)
Line 38: Line 34:
 
<div style="width: 27%; float: left; padding-right: 3%;">
 
<div style="width: 27%; float: left; padding-right: 3%;">
 
<h3>Progress</h3>
 
<h3>Progress</h3>
* Skeleton full-screen module is added: https://github.com/SlicerIGT/SliceletTools
+
* Guidance slicelet = guidelet base class is added to https://github.com/SlicerIGT/SlicerIGT, guidelets are added: https://github.com/SlicerIGT/LumpNav and https://github.com/SlicerIGT/ProstateNav
 
* [http://1drv.ms/1dwQfEr Sample sequence] (can be replayed using [http://www.plustoolkit.org PlusServer])
 
* [http://1drv.ms/1dwQfEr Sample sequence] (can be replayed using [http://www.plustoolkit.org PlusServer])
 +
* Collected information of several groups about common needs
 +
** Start in full screen
 +
** Save/load scene
 +
** Import pre-operative image (DICOM and non-DICOM)
 +
** Device control through Plus: live image and/or tracking acquisition, start/stop recording (record procedure - live images, tool positions), volume reconstruction
 +
** Switch between layouts
 +
** Switch between simplified/full slicer GUI
 +
** Send Plus configuration files to Plus
 +
** Create abstract workflow section and step; automatic transition to state; disable/show warning if prerequisites are not met
 +
** View-point, bulls-eye view
 +
** Edit application configuration
 +
* Created base class that is ready to be used for prototyping US-guided procedures
 
</div>
 
</div>
 
</div>
 
</div>

Latest revision as of 13:50, 17 July 2015

Home < 2015 Summer Project Week:IGTSliceletBase

Key Investigators

  • Andras Lasso
  • Andrey Fedorov
  • Adam Rankin
  • Jayender Jagadeesan
  • Laszlo Kanyasi

Project Description

Objective

  • Generalize current Slicer-based intra-operative/surgical applications that are already successfully translated to the operating room
  • Create base classes and utility functions for easy implementation of slicelets/full-screen modules that are convenient to use in the operating room, running on tablets and laptops

Approach, Plan

  • Questions:
    • Slicelet/full-screen module, docking widgets (slicelets seem to have performance issue and it's difficult to make sure nothing relies on main window, status bar, etc.)
    • Scene initialization: create empty scene/activate loaded scene
    • How to split code to multiple files but still allow reloading (similarly to Editor?)
    • What are the minimum set of modules required for basic operation of Slicer
    • How to create logic class without activating the GUI
  • Create base classes and/or utility classes
  • Create intra-operative US/MRI prostate registration slicelet

Progress

  • Guidance slicelet = guidelet base class is added to https://github.com/SlicerIGT/SlicerIGT, guidelets are added: https://github.com/SlicerIGT/LumpNav and https://github.com/SlicerIGT/ProstateNav
  • Sample sequence (can be replayed using PlusServer)
  • Collected information of several groups about common needs
    • Start in full screen
    • Save/load scene
    • Import pre-operative image (DICOM and non-DICOM)
    • Device control through Plus: live image and/or tracking acquisition, start/stop recording (record procedure - live images, tool positions), volume reconstruction
    • Switch between layouts
    • Switch between simplified/full slicer GUI
    • Send Plus configuration files to Plus
    • Create abstract workflow section and step; automatic transition to state; disable/show warning if prerequisites are not met
    • View-point, bulls-eye view
    • Edit application configuration
  • Created base class that is ready to be used for prototyping US-guided procedures