Difference between revisions of "Volume Rendering"
From NAMIC Wiki
| (One intermediate revision by one other user not shown) | |||
| Line 1: | Line 1: | ||
{| | {| | ||
| − | |[[Image: | + | |[[Image:Mouse-colon-tumor.png|thumb|320px|Return to [[2009_Winter_Project_Week|Project Week Main Page]] ]] |
|} | |} | ||
| Line 39: | Line 39: | ||
<h1>Progress</h1> | <h1>Progress</h1> | ||
| − | * Yanling and Curt integrated | + | * Yanling and Curt integrated GPU based volume rendering algorithm into Slicer3 |
* Yanling, Curt and Alex discussed a plan for re-design: | * Yanling, Curt and Alex discussed a plan for re-design: | ||
** MRML nodes for ROI, transfer functions, lut's, parameters (Alex) | ** MRML nodes for ROI, transfer functions, lut's, parameters (Alex) | ||
Latest revision as of 08:57, 9 January 2009
Home < Volume Rendering Return to Project Week Main Page |
Key Investigators
- Isomics:Alex, Steve
- KnowledgeVis: Curt Lisle
- NCI: Yanling Liu
Objective
Revise the current Volume Rendering module through the inclusion of new rendering methods. Simplify the code implementation while trying to preserve the good interaction ideas which were implemented already.
Approach, Plan
- Separate code into GUI-MRML-Logic components architecture.
- Create reusable components for clipping with ROI.
- Provide persistence/reuse of transfer functions and their MRML representation.
- Enable easy integration of other volume rendering techniques.
Progress
- Yanling and Curt integrated GPU based volume rendering algorithm into Slicer3
- Yanling, Curt and Alex discussed a plan for re-design:
- MRML nodes for ROI, transfer functions, lut's, parameters (Alex)
- GUI separation, widgets for separate components (Alex)
- Volume rendering pipeline and logic (Yanling, Curt, Alex)
