Difference between revisions of "Slicer3:Volume Rendering"
From NAMIC Wiki
m (→Goals) |
m |
||
Line 1: | Line 1: | ||
== Overview == | == Overview == | ||
− | + | ==next Tasks== | |
+ | *Add a vtkSlicerNodeWidget to prototype | ||
+ | *Have a closer look at vtkSlicerViewerWidget | ||
+ | *MRML Scene | ||
== Goals == | == Goals == | ||
Line 24: | Line 27: | ||
* Level of detail rendering | * Level of detail rendering | ||
* Proper integration with surface rendering | * Proper integration with surface rendering | ||
+ | |||
+ | Different Volume Rendering Algorithms | ||
+ | *RayCast | ||
+ | *2D Texture Mapping | ||
+ | *3D Texture Mapping | ||
+ | *... | ||
== Wish List == | == Wish List == |
Revision as of 18:41, 22 August 2007
Home < Slicer3:Volume RenderingContents
Overview
next Tasks
- Add a vtkSlicerNodeWidget to prototype
- Have a closer look at vtkSlicerViewerWidget
- MRML Scene
Goals
Volume rendering presets :
- MIP (Maximum Intensity Projection)
- CT Bone and vessel
- Use histogram and tresholds, find possibilities to avoid outliers
- T1 MR Air/skin interface
- Label map per-label object rendering
- Possible starting points for this task: vtkMRMLVolumeNode
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