Difference between revisions of "Projects/Slicer3/2007 Project Week Display Optimization"

From NAMIC Wiki
Jump to: navigation, search
m
Line 17: Line 17:
 
<div style="width: 27%; float: left; padding-right: 3%;">
 
<div style="width: 27%; float: left; padding-right: 3%;">
 
<h1>Approach, Plan</h1>
 
<h1>Approach, Plan</h1>
</div>
 
 
<div style="width: 40%; float: left;">
 
 
# doing the resample to a 'native' size for the input volume and then upsampling to screen size still sounds best.
 
# doing the resample to a 'native' size for the input volume and then upsampling to screen size still sounds best.
 
# using a vtkImageActor in the vtkSlicerSliceViewer (instead of the current vtkImageMapper and vtkActor2D) is likely to be faster, and can do the upsample needed in step (1),
 
# using a vtkImageActor in the vtkSlicerSliceViewer (instead of the current vtkImageMapper and vtkActor2D) is likely to be faster, and can do the upsample needed in step (1),
Line 25: Line 22:
 
# David thinks we should be able to use the existing functions of vtkImageReslice to get the background mask.  He didn't thing having a two-output filter was a good idea based on his experience with the way the vtk pipeline executes.
 
# David thinks we should be able to use the existing functions of vtkImageReslice to get the background mask.  He didn't thing having a two-output filter was a good idea based on his experience with the way the vtk pipeline executes.
  
 +
</div>
 +
 +
<div style="width: 40%; float: left;">
 
<h1>Progress</h1>
 
<h1>Progress</h1>
 
</div>
 
</div>

Revision as of 16:34, 30 May 2007

Home < Projects < Slicer3 < 2007 Project Week Display Optimization


Key Investigators

  • SPL: Raimundo Sierra, David Gobbi, Steve Pieper


Objective

Improving the performance of slicer display

Approach, Plan

  1. doing the resample to a 'native' size for the input volume and then upsampling to screen size still sounds best.
  2. using a vtkImageActor in the vtkSlicerSliceViewer (instead of the current vtkImageMapper and vtkActor2D) is likely to be faster, and can do the upsample needed in step (1),
  3. using a vtkImageActor for the slice model in the vtkSlicerViewer will bypass the power-of-2 resampling in vtkTexture that gives the artifacts I hate
  4. David thinks we should be able to use the existing functions of vtkImageReslice to get the background mask. He didn't thing having a two-output filter was a good idea based on his experience with the way the vtk pipeline executes.

Progress



References

Additional Information

Slides with diagrams about the slicer rendering pipeline