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

From NAMIC Wiki
Jump to: navigation, search
 
Line 29: Line 29:
 
* HoloLens deemed not worth the effort at this time
 
* HoloLens deemed not worth the effort at this time
 
* Discussion changed to OpenVR integration as a visualization platform from Slicer
 
* Discussion changed to OpenVR integration as a visualization platform from Slicer
** 20% - Upgrade Slicer to VTK >= 553a8bc0dd32889cc0eef49f2462e9b7e7ae81e3 (updated OpenVR support)
+
** 30% - Upgrade Slicer to VTK >= 553a8bc0dd32889cc0eef49f2462e9b7e7ae81e3 (updated OpenVR support)
 +
*** Slicer upgrade to using OpenGL2 backend (required for OpenVR)
 +
** 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
 
*** SuperBuild expand to include OpenVR - https://github.com/ValveSoftware/openvr.git
 
*** SuperBuild expand to include OpenVR - https://github.com/ValveSoftware/openvr.git
 
*** SuperBuild expand to include SDL2 - https://github.com/spurious/SDL-mirror.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...
+
** 50% - Extend Slicer to use new OpenVR related classes
*** 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...
 
*** Create classes qMRMLVRView, qMRMLVRWidget, etc...
 
*** Update layout manager to support new view type
 
*** Update layout manager to support new view type

Latest revision as of 17:09, 15 January 2017

Home < 2017 Winter Project Week < Slicer VR

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/Kitware expert (help needed)
  • 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
    • 30% - Upgrade Slicer to VTK >= 553a8bc0dd32889cc0eef49f2462e9b7e7ae81e3 (updated OpenVR support)
      • Slicer upgrade to using OpenGL2 backend (required for OpenVR)
    • 20% - Enable support for a single application to instantiate multiple factory overrides of vtkRenderer, vtkRenderWindow, etc...
    • 50% - Extend Slicer to use new OpenVR related classes
      • Create classes qMRMLVRView, qMRMLVRWidget, etc...
      • Update layout manager to support new view type

Background and References