Difference between revisions of "2016 Summer Project Week/SliceTracker"

From NAMIC Wiki
Jump to: navigation, search
 
(4 intermediate revisions by 2 users not shown)
Line 20: Line 20:
 
* Use SliceTracker currently used in shadow mode + collecting feedback from Kemal about usability
 
* Use SliceTracker currently used in shadow mode + collecting feedback from Kemal about usability
 
** At least 5 cases in a row which has to run without having any issues, then production use
 
** At least 5 cases in a row which has to run without having any issues, then production use
* Integration of Z-Frame registration
+
* Integration of [https://github.com/SlicerProstate/SliceTracker/tree/master/ZFrameCalibration Z-Frame registration]
 
* Calculation of template hole and depth to apply for reaching targets
 
* Calculation of template hole and depth to apply for reaching targets
 
|
 
|
Line 27: Line 27:
 
|
 
|
 
<!-- Progress and Next steps bullet points (fill out at the end of project week) -->
 
<!-- Progress and Next steps bullet points (fill out at the end of project week) -->
* Discussions about implementing SliceTracker as a Slicelet (for prevent users from making mistakes/pushing wrong buttons etc.)
+
* Discussions about implementing SliceTracker as a Slicelet (this will prevent users from making mistakes/pushing wrong buttons etc.)
* Will soon run in production mode replacing the "old" Slicer 3 cart
+
* Next Steps:
 +
** Will soon run in production mode replacing the "old" Slicer 3 cart
 +
** As soon as it is in its final state: create extension
 
|}
 
|}
  
Line 38: Line 40:
  
 
SliceTracker code: https://github.com/SlicerProstate/SliceTracker
 
SliceTracker code: https://github.com/SlicerProstate/SliceTracker
 +
 +
Previous project week resources:
 +
* Winter 2015: http://www.na-mic.org/Wiki/index.php/ProstateNavigation_workflow
 +
* Summer 2015: http://www.na-mic.org/Wiki/index.php/2015_Refinement_Registration_Module
 +
* Winter 2016: http://www.na-mic.org/Wiki/index.php/2016_Winter_Project_Week/Projects/SliceTracker

Latest revision as of 15:52, 25 June 2016

Home < 2016 Summer Project Week < SliceTracker

Key Investigators

  • Christian Herz (BWH)
  • Peter Behringer (Basler AG)
  • Andriy Fedorov (BWH)

Project Description

Slicetracker is a Slicer extension which focuses on tracking the prostate during MR-guided prostate biopsies. It combines registration of the prostate in pre-procedural and intra-procedural images which improves the chance to find the exact same target position in intra-procedural images.

Furthermore a so called z-Frame registration is included for correlating the patient and 3D Slicers coordinate system. For guidance of the needle a template grid with 15x14 holes is placed in front of the z-Frame. The optimal hole is computed for inserting the needle and obtaining the tissue sample.

Objective Approach and Plan Progress and Next Steps
  • Use SliceTracker currently used in shadow mode + collecting feedback from Kemal about usability
    • At least 5 cases in a row which has to run without having any issues, then production use
  • Integration of Z-Frame registration
  • Calculation of template hole and depth to apply for reaching targets
  • Discussions and feedback about usability and improvements
  • Discussions about implementing SliceTracker as a Slicelet (this will prevent users from making mistakes/pushing wrong buttons etc.)
  • Next Steps:
    • Will soon run in production mode replacing the "old" Slicer 3 cart
    • As soon as it is in its final state: create extension

Background and References

Slicetracker.gif


SliceTracker code: https://github.com/SlicerProstate/SliceTracker

Previous project week resources: