Difference between revisions of "2017 Winter Project Week/Slicer HoloLens"

From NAMIC Wiki
Jump to: navigation, search
(Created page with "__NOTOC__ <gallery> Image:PW-Winter2017.png|link=2017_Winter_Project_Week#Projects|Projects List <!-- Use the "Upload file" link on the l...")
 
 
Line 7: Line 7:
 
==Key Investigators==
 
==Key Investigators==
 
* Adam Rankin (Robarts Research Institute, Canada)
 
* Adam Rankin (Robarts Research Institute, Canada)
 +
* Ryan D'Souza (Northern Digital Inc., Canada - External)
 +
* Matthew Jolley (Children's Hospital of Philadelphia - doesn't know it yet)
 +
* Slicer UI/Rendering expert (help needed)
  
 
==Project Description==
 
==Project Description==
Line 20: Line 23:
 
|
 
|
 
<!-- Approach and Plan bullet points -->
 
<!-- Approach and Plan bullet points -->
*  
+
* Discuss with other interested parties the value of HoloLens integration
 
|
 
|
 
<!-- 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 -->
*
+
* HoloLens deemed not worth the effort at this time
 +
* Discussion changed to OpenVR integration as a visualization platform from Slicer
 +
** Identification of relevant steps to enable OpenVR output from Slicer
 +
*** 20% - Upgrade Slicer to VTK >= 553a8bc0dd32889cc0eef49f2462e9b7e7ae81e3 (updated OpenVR support)
 +
**** SuperBuild expand to include OpenVR - https://github.com/ValveSoftware/openvr.git
 +
**** SuperBuild expand to include SDL2 - https://github.com/spurious/SDL-mirror.git
 +
*** 20% - Enable support for a single application to instantiate multiple factory overrides of vtkRenderer, vtkRenderWindow, etc...
 +
**** Subclass ctkVTKRenderView, ctkVTKAbstractView with -> ctkVTKVRRenderView, ctkVTKVRAbstractView such that they instantiate vtkOpenVRRenderer, vtkOpenVRRenderWindow, etc... instead of factory overridden default
 +
*** 60% - Extend Slicer to use new OpenVR related classes
 +
**** Create classes qMRMLVRView, qMRMLVRWidget, etc...
 +
**** Update layout manager to support new view type
 
|}
 
|}
  
 
==Background and References==
 
==Background and References==
 
<!-- Use this space for information that may help people better understand your project, like links to papers, source code, or data -->
 
<!-- Use this space for information that may help people better understand your project, like links to papers, source code, or data -->

Latest revision as of 19:03, 12 January 2017

Home < 2017 Winter Project Week < Slicer HoloLens

Key Investigators

  • Adam Rankin (Robarts Research Institute, Canada)
  • Ryan D'Souza (Northern Digital Inc., Canada - External)
  • Matthew Jolley (Children's Hospital of Philadelphia - doesn't know it yet)
  • Slicer UI/Rendering expert (help needed)

Project Description

Objective Approach and Plan Progress and Next Steps
  • Discuss with other interested parties the value of HoloLens integration
  • HoloLens deemed not worth the effort at this time
  • Discussion changed to OpenVR integration as a visualization platform from Slicer
    • Identification of relevant steps to enable OpenVR output from Slicer
      • 20% - Upgrade Slicer to VTK >= 553a8bc0dd32889cc0eef49f2462e9b7e7ae81e3 (updated OpenVR support)
      • 20% - Enable support for a single application to instantiate multiple factory overrides of vtkRenderer, vtkRenderWindow, etc...
        • Subclass ctkVTKRenderView, ctkVTKAbstractView with -> ctkVTKVRRenderView, ctkVTKVRAbstractView such that they instantiate vtkOpenVRRenderer, vtkOpenVRRenderWindow, etc... instead of factory overridden default
      • 60% - Extend Slicer to use new OpenVR related classes
        • Create classes qMRMLVRView, qMRMLVRWidget, etc...
        • Update layout manager to support new view type

Background and References