Slicer3:Volume Rendering

Overview

The topic of the new Volume Rendering Module is the integration of hardware accelerated volume rendering. There is a special focus of achieving interactive update rates, easy user interaction (e.g. by offering several presets) and the use of label maps. Goals also include incremental updates (if module is used with Editor module), saving and loading of the configuration etc.

Archtecture/Design

Use Case Diagram

How to compile the module

• Switch the compile option "VolumeRenderingModule" on (in cmake)
• Make sure that you recompile "Slicer3.cxx"
• Compile

Current Features

• Visualize grayscale volumes
• Create Visualization Parameter sets, load and save them
• Use preset Visualization Parameter sets and link already created Parameter sets with current Volume

Latest results and limitations

Description

• Loading changing of MRML-Nodes is possible during runtime
• At the moment no removing of MRML-Nodes possible
• Change properties (Shading, Interpolation, mapping)
• Calculate transfer functions automatically
• Performance:
  • Interrupting is possible in render window.
  • Interrupting somewhere else requires platform dependent coding (q.v. problems)
• Cropping is possible

Screenshots

volume rendered label map of the tutorial dataset

volume rendered label map of the tutorial dataset, shading enabled

shading enabled, linear interpolation, automatich mapping for bones

Goals

Volume rendering presets :

• MIP (Maximum Intensity Projection)
  • Wikipedia
  • vtkFixedPointVolumeRayCastMapper Class Reference
• CT Bone and vessel
  • Use Hounsfield units
    • Bone +400->+1000
    • Soft tissue +40->+80
    • Water 0
    • Fat -60->-100
    • Lung -400->-600
    • Air -1000
  • Problem with Vessels: Different contrast mediums?!
• T1 MR Air/skin interface
• Label map per-label object rendering

Slicer3 module interface:

• Select from loaded volumes
• Specify preset transfer functions or use KWWidgets tools

Slicer3 internals:

• Correct coordinates including transforms
• Level of detail rendering
• Proper integration with surface rendering

Different Volume Rendering Algorithms

• RayCast
• 2D Texture Mapping
• 3D Texture Mapping
• ...

Wish List

• 2D Transfer functions - may require specialized opengl code integrated with VTK. Talk with Gordon about latest work from Utah.

• use glTexSubImage3D so that incremental changes to the volume can be quickly reflected

• use distance maps (inlcude several components) in rendering

Glossar

• Visualization Parameter Set