Difference between revisions of "Slicer3:Volume Rendering With Cuda"

From NAMIC Wiki
Jump to: navigation, search
Line 10: Line 10:
 
#Create a '''user interface''' to control the flow of the Volume Rendering within Slicer3.
 
#Create a '''user interface''' to control the flow of the Volume Rendering within Slicer3.
  
== VTK Cuda Runtime API support ==
+
= VTK Cuda Runtime API support =
 
The c-interface to the CUDA objects and functions will be wrapped as described on the following pages:
 
The c-interface to the CUDA objects and functions will be wrapped as described on the following pages:
 
*[[VTK Cuda Wrapper Classes]]
 
*[[VTK Cuda Wrapper Classes]]
 
*[[VTK Cuda Memory Management Classes]]
 
*[[VTK Cuda Memory Management Classes]]
  
== Cuda Volume Rendering Algorithm ==
+
= Cuda Volume Rendering Algorithm =
 
The Code that we use so far has been implemented by Nicholas Harlambang and can be viewed at [http://svn.orxonox.net/subprojects/volrenSample].
 
The Code that we use so far has been implemented by Nicholas Harlambang and can be viewed at [http://svn.orxonox.net/subprojects/volrenSample].
  
== VTK Modules and Pipeline ==
+
= VTK Modules and Pipeline =
 
These are the modules that will be created in order to integrate a Cuda based Volume Rendering into the Slicer3 pipeline
 
These are the modules that will be created in order to integrate a Cuda based Volume Rendering into the Slicer3 pipeline
 
# '''A [http://www.vtk.org/doc/release/5.0/html/a01572.html vtkImageReader]:''' to read Volume data as any kind of Volume Data
 
# '''A [http://www.vtk.org/doc/release/5.0/html/a01572.html vtkImageReader]:''' to read Volume data as any kind of Volume Data
Line 40: Line 40:
 
* Blue colored fields are specially implemented parts for the communication of cuda and vtk and the volume rendering algorithms.
 
* Blue colored fields are specially implemented parts for the communication of cuda and vtk and the volume rendering algorithms.
  
== A Slicer3 User Interface ==
+
= A Slicer3 User Interface =
 
The GUI will be designed using KWWidgets. With this the user will be able to change the rendering resolution, step size, control the color sceme and load and store further information.
 
The GUI will be designed using KWWidgets. With this the user will be able to change the rendering resolution, step size, control the color sceme and load and store further information.
  
 +
= Tasks and timeline =
 
== Tasks ==
 
== Tasks ==
 
#Proof of concept
 
#Proof of concept

Revision as of 20:42, 28 December 2007

Home < Slicer3:Volume Rendering With Cuda

Objectives

The goal of this project is to implement a CUDA based Volume Rendering Technique inside of VTK and Slicer3.


Project Outline

Several steps have to be made to integrating a CUDA based volume rendering technique into vtk.

  1. Integrate CUDA runtime API support into VTK using a class based approach.
  2. Implement and Integrate a CUDA Volume Rendering algorithm.
  3. Integrate the algorithm into a VTK pipeline (described below)
  4. Create a user interface to control the flow of the Volume Rendering within Slicer3.

VTK Cuda Runtime API support

The c-interface to the CUDA objects and functions will be wrapped as described on the following pages:

Cuda Volume Rendering Algorithm

The Code that we use so far has been implemented by Nicholas Harlambang and can be viewed at [1].

VTK Modules and Pipeline

These are the modules that will be created in order to integrate a Cuda based Volume Rendering into the Slicer3 pipeline

  1. A vtkImageReader: to read Volume data as any kind of Volume Data
  2. A vtkCudaImageFilter: A Filter to convert from the reader output to a cuda-able DataSet
  3. A vtkCudaDataSet: A new vtkDataSet where that holds and handles the data transfer from and to one or multiple CUDA devices.
  4. A vtkCudaVolumeMapper: A new vtkVolumeMapper that renders the scene using the
    1. lighting model
    2. a prepared Z buffer
    3. a camera position
    4. A [vtkTexture] and a Plane to render the result to
  5. An actor that places the volume into the scene
  6. Chain this pipeline together and attach it to a rendering window.

In the following image the pipeline is displayed together with the connections from the VTK, Slicer3 and CUDA frameworks. VtkCudaVolumeRenderingPipeline.png

Description:

  • The Fat line displays the pipeline flow.
  • Green colored fields are classes from the Slicer3 or vtk implementation
  • Red colored fields are CUDA and hardware specific parts
  • Blue colored fields are specially implemented parts for the communication of cuda and vtk and the volume rendering algorithms.

A Slicer3 User Interface

The GUI will be designed using KWWidgets. With this the user will be able to change the rendering resolution, step size, control the color sceme and load and store further information.

Tasks and timeline

Tasks

  1. Proof of concept
  2. Integrate into VTK
    1. Render the output from the code of Nicholas volume render sample into vtkImageViewer
    2. Adapt to Z-buffer
    3. Adapt lighting model
    4. Adapt to input Image
  3. Integration into Slicer

Timeline

From To Task
12/01/07 05/31/08 Master Thesis Duration
12/01/07 12/31/07 Reading into the Project, Defining Basic Classes
01/01/08 01/06/08 Basic Class Definition Ready for Hands on Meeting
01/07/08 01/12/08 Hands on meeting in Salt Lake City
01/14/08 02/01/08 Further Implementation

Resources

  1. For testing purposes: File:Heart256.raw Store this file in Slicer3/Modules/VolumeRenderingCuda/Testing/heart256.raw
  2. Also checkout the main project page at Slicer-IGT/GPU-IGT