Difference between revisions of "2011 Winter Project Week: Slice View Performance"
(Created page with '__NOTOC__ <gallery> Image:PW-SLC2011.png|Projects List </gallery> ==Key Investigators== * Will, Jc - Kitware * Luca - Orobix * Steve - Isom…') |
|||
| Line 10: | Line 10: | ||
<div style="margin: 20px;"> | <div style="margin: 20px;"> | ||
| − | <div style="width: | + | <div style="width: 27%; float: left; padding-right: 3%;"> |
<h3>Objective</h3> | <h3>Objective</h3> | ||
| Line 18: | Line 18: | ||
</div> | </div> | ||
| − | <div style="width: | + | <div style="width: 27%; float: left; padding-right: 3%;"> |
<h3>Approach, Plan</h3> | <h3>Approach, Plan</h3> | ||
Revision as of 23:20, 14 December 2010
Home < 2011 Winter Project Week: Slice View Performance
Key Investigators
- Will, Jc - Kitware
- Luca - Orobix
- Steve - Isomics
Objective
Explore slice rendering pipeline to optimize amount of reslicing and compositing vs. opengl render time. Goal is to come up with a good vtk pipeline that can be implemented in both slicer3 and slicer4.
Currently, slices are extracted from volumes at the resolution of the slice view window. Typically these match fairly well, with, for example, a 640x480 slice image being extracted from a 512^3 volume, However in some cases one may wish to display a 256^3 volume on a 2kx2k monitor. In this case the trilinear interpolation and layer compositing operations are wasteful.
Approach, Plan
The goal it to consider introducing an intermediate resampling step at a resolution that is appropriate for the input volumes and then using the graphics hardware to do the final resample to screen space. A vtkImageActor is probably the correct class for this.
This will need to be incorporated into the ctkLightBoxManager class.
Progress
Some prototyping has been done.
