Difference between revisions of "2016 Winter Project Week/Projects/SliceTracker"

From NAMIC Wiki
Jump to: navigation, search
 
m
 
(16 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 +
<gallery>
 +
Image:PW-MIT2016.png|link=2016_Winter_Project_Week#Projects|[[2016_Winter_Project_Week#Projects|Projects List]]
 +
<!-- Use the "Upload file" link on the left and then add a line to this list like "File:MyAlgorithmScreenshot.png" -->
 +
Image:2016WinterEBP_SliceTracker.jpg|SliceTracker Main Window Screenshot
 +
Image:2016WinterEBP_SliceTracker_1.jpg|SliceTracker Evaluation Window Screenshot</gallery>
 +
 
==Key Investigators==
 
==Key Investigators==
 
* Christian Herz (BWH)
 
* Christian Herz (BWH)
 
* Andriy Fedorov (BWH)
 
* Andriy Fedorov (BWH)
 +
* Andras Lasso (Queens)
 +
 +
==Project Description==
 +
Prostate biopsies can become a big challenge, especially when the prostate changed from pre-procedural to intra-procedural image acquisition. Motion and deformation of the prostate raises difficulties for positioning the biopsy needle at the right position. The registration module’s goal is to optimize the workflow and provide a solution, that is easy to use.
 +
{| class="wikitable"
 +
! style="text-align: left; width:27%" |  Objective
 +
! style="text-align: left; width:27%" |  Approach and Plan
 +
! style="text-align: left; width:27%" |  Progress and Next Steps
 +
|- style="vertical-align:top;"
 +
|
 +
<!-- Objective bullet points -->
 +
* Slicer module implemented that allows the registration of the prostate
 +
* Use SliceTracker during prostate biopsies as a replacement to current approach
 +
|
 +
<!-- Approach and Plan bullet points -->
 +
* Present the module to interested members of the community
 +
* Get feedback about the workflow and usability
 +
* Work on the remaining issues
 +
* Discuss about migrating this module into a slicelet
 +
|
 +
<!-- Progress and Next steps bullet points (fill out at the end of project week) -->
 +
* Positive feedback for workflow and usability of the module
 +
* LumpNav is a slicelet example to follow
 +
* TODO:
 +
** Create an extension from that module and provide an appropriate example dataset
 +
** Integrate the z-frame and navigation component into the module
 +
|}
 +
 +
==Progress notes==
 +
* What about simply hiding components (toolbars) that are not needed?
 +
* Trick to hide all toolbars!
 +
<pre>
 +
>>> w = slicer.util.mainWindow()
 +
>>> for c in w.children():
 +
...  if str(type(c)).find('ToolBar')>0:
 +
...    c.hide()
 +
</pre>
 +
 +
Drawback: after restarting Slicer, the toolbars are still hidden.
 +
 +
==Background and References==
 +
<!-- Use this space for information that may help people better understand your project, like links to papers, source code, or data -->
 +
SliceTracker code: https://github.com/SlicerProstate/SliceTracker

Latest revision as of 15:10, 8 January 2016

Home < 2016 Winter Project Week < Projects < SliceTracker

  • SliceTracker Main Window Screenshot

  • SliceTracker Evaluation Window Screenshot

Key Investigators

  • Christian Herz (BWH)
  • Andriy Fedorov (BWH)
  • Andras Lasso (Queens)

Project Description

Prostate biopsies can become a big challenge, especially when the prostate changed from pre-procedural to intra-procedural image acquisition. Motion and deformation of the prostate raises difficulties for positioning the biopsy needle at the right position. The registration module’s goal is to optimize the workflow and provide a solution, that is easy to use.

Objective Approach and Plan Progress and Next Steps
  • Slicer module implemented that allows the registration of the prostate
  • Use SliceTracker during prostate biopsies as a replacement to current approach
  • Present the module to interested members of the community
  • Get feedback about the workflow and usability
  • Work on the remaining issues
  • Discuss about migrating this module into a slicelet
  • Positive feedback for workflow and usability of the module
  • LumpNav is a slicelet example to follow
  • TODO:
    • Create an extension from that module and provide an appropriate example dataset
    • Integrate the z-frame and navigation component into the module

Progress notes

  • What about simply hiding components (toolbars) that are not needed?
  • Trick to hide all toolbars!
>>> w = slicer.util.mainWindow()
>>> for c in w.children():
...   if str(type(c)).find('ToolBar')>0:
...     c.hide()

Drawback: after restarting Slicer, the toolbars are still hidden.

Background and References

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

Retrieved from "https://www.na-mic.org/w/index.php?title=2016_Winter_Project_Week/Projects/SliceTracker&oldid=92044"