Difference between revisions of "Projects/Slicer3/2007 Project Week Display Optimization"
From NAMIC Wiki
| Line 20: | Line 20: | ||
<div style="width: 40%; float: left;"> | <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. | ||
| + | # 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 for the slice model in the vtkSlicerViewer will bypass the power-of-2 resampling in vtkTexture that gives the artifacts I hate | ||
| + | # 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. | ||
| + | |||
<h1>Progress</h1> | <h1>Progress</h1> | ||
</div> | </div> | ||
Revision as of 16:33, 30 May 2007
Home < Projects < Slicer3 < 2007 Project Week Display Optimization Return to Project Week Main Page |
Key Investigators
- SPL: Raimundo Sierra, David Gobbi, Steve Pieper
Objective
Improving the performance of slicer display
Approach, Plan
- 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 for the slice model in the vtkSlicerViewer will bypass the power-of-2 resampling in vtkTexture that gives the artifacts I hate
- 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
