Difference between revisions of "Projects/Slicer3/2007 Project Week Display Optimization"
From NAMIC Wiki
| (7 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
| − | + | {| | |
| + | |[[Image:ProjectWeek-2007.png|thumb|320px|Return to [[2007_Programming/Project_Week_MIT|Project Week Main Page]] ]] | ||
| + | |[[Image:Programming_Week_RS_Slide4.JPG|thumb|240px|Previous rendering pipeline]] | ||
| + | |[[Image:Programming_Week_RS_Slide6.JPG|thumb|240px|Now]] | ||
| + | |} | ||
| + | |||
| + | __NOTOC__ | ||
| + | ===Key Investigators=== | ||
| + | * SPL: Raimundo Sierra, David Gobbi, Steve Pieper | ||
| + | |||
| + | |||
| + | <div style="margin: 20px;"> | ||
| + | |||
| + | <div style="width: 27%; float: left; padding-right: 3%;"> | ||
| + | <h1>Objective</h1> | ||
| + | Improving the performance of slicer display | ||
| + | |||
| + | </div> | ||
| + | <div style="width: 27%; float: left; padding-right: 3%;"> | ||
| + | <h1>Approach, Plan</h1> | ||
| + | # 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. | ||
| + | |||
| + | </div> | ||
| + | |||
| + | <div style="width: 40%; float: left;"> | ||
| + | <h1>Progress</h1> | ||
| + | # Implemented filter with aditional output, significantly faster rendering of slices | ||
| + | # Integrated building of alpha mask into one filter in form of a derived class from vtkReslice -> avoids multiple iterations through dataset | ||
| + | # TODO: integrate map to color and map to window level | ||
| + | |||
| + | </div> | ||
| + | <br style="clear: both;" /> | ||
| + | </div> | ||
| + | |||
| + | |||
| + | ===References=== | ||
==Additional Information== | ==Additional Information== | ||
| − | + | [[Media:Slicer_Rendering.ppt | Slides with diagrams about the slicer rendering pipeline]] | |
| − | |||
Latest revision as of 14:02, 29 June 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
- Implemented filter with aditional output, significantly faster rendering of slices
- Integrated building of alpha mask into one filter in form of a derived class from vtkReslice -> avoids multiple iterations through dataset
- TODO: integrate map to color and map to window level
