Difference between revisions of "Project Week 25/Next Generation GPU Volume Rendering"

From NAMIC Wiki
Jump to: navigation, search
Line 7: Line 7:
  
 
* [http://nist.mni.mcgill.ca/?page_id=369 Simon Drouin] (Montreal Neurological Institute, Canada)
 
* [http://nist.mni.mcgill.ca/?page_id=369 Simon Drouin] (Montreal Neurological Institute, Canada)
* [http://www.spl.harvard.edu/pages/People/pieper Steve Pieper ] (Isomics Inc., Cambridge, MA)
+
* [http://www.spl.harvard.edu/pages/People/pieper Steve Pieper ] (Isomics Inc., USA)
 
* [http://perk.cs.queensu.ca/users/lasso Andras Lasso] (Queen's University, Canada)
 
* [http://perk.cs.queensu.ca/users/lasso Andras Lasso] (Queen's University, Canada)
 
* [http://www.sintef.no/en/all-employees/employee/?empId=541 Ole Vegard Solberg] (SINTEF, Norway)
 
* [http://www.sintef.no/en/all-employees/employee/?empId=541 Ole Vegard Solberg] (SINTEF, Norway)

Revision as of 13:56, 8 June 2017

Home < Project Week 25 < Next Generation GPU Volume Rendering


Back to Projects List


Key Investigators

Project Description

Objective Approach and Plan Progress and Next Steps

Develop a specification for the next generation of GPU volume processing and rendering in VTK and Slicer

The specification should support

  • Multiple input volumes for ray-casting and slice-based volume rendering
  • GPU-based volume slicing and compositing
  • Programmable volume rendering shader
  • Smart management of volumes in GPU memory
  • Possibility to run simple processing operations on the volume (e.g. Non-linear transforms)
  • Consider possible complications
    • GPU features not available / software only fallback
    • Volumes too big to for GPU memory

Compare the architectures of different existing projects where parts of the required functionality has been implemented:

Determine a sensible way to integrate all those contribution in VTK.

TODO

Illustrations

Background and References