Difference between revisions of "2008 Winter Project Week VolumeRendering"

From NAMIC Wiki
Jump to: navigation, search
 
m (Text replacement - "http://www.slicer.org/slicerWiki/index.php/" to "https://www.slicer.org/wiki/")
 
(12 intermediate revisions by 3 users not shown)
Line 1: Line 1:
 
{|
 
{|
 
|[[Image:NAMIC-SLC.jpg|thumb|320px|Return to [[2008_Winter_Project_Week]] ]]
 
|[[Image:NAMIC-SLC.jpg|thumb|320px|Return to [[2008_Winter_Project_Week]] ]]
|valign="top"|[[Image:Case24-coronal-tensors-edit.png |thumb|320px|The Cingulum Bundle Anchor Tract]]
+
|valign="top"|[[Image:AbdomenLung.jpg |thumb|320px|Volume Rendering, mapping functions optimized for lung]]
 +
|valign="top"|[[Image:VolumeRenderingBoxWidget.jpg |thumb|320px|Edit clipping planes using vtkBoxWidget]]
 
|}
 
|}
  
 
__NOTOC__
 
__NOTOC__
 
===Key Investigators===
 
===Key Investigators===
* Insomics: Steve Pieper
+
* Isomics: Steve Pieper
 
* SPL/IGT: Benjamin Grauer, Andreas Freudling
 
* SPL/IGT: Benjamin Grauer, Andreas Freudling
  
Line 14: Line 15:
  
 
<h1>Objective</h1>
 
<h1>Objective</h1>
We have developed techniques for finding the optimal geodesic path (or anchor tract) between two regions of interest in DWMRI data.
+
Integration of interactive volume rendering into Slicer 3 using hardware and software based rendering techniques.
  
The objectives of this project are to port the Fast Sweeping and optimal geodesic path tractography code to ITK as well as the code to provide for volumetric segmentation of DW-MRI data.
+
Improve the existing framework using new algorithms / frameworks like [http://en.wikipedia.org/wiki/CUDA| CUDA] or other rendering algorithms.
  
See our [[Algorithm:GATech:Finsler_Active_Contour_DWI| Project Page]] for more details.
+
Use volume rendering for 4D IGT.
 +
 
 +
See [https://www.slicer.org/wiki/Slicer3:Volume_Rendering integration of volume rendering in Slicer 3] and [http://www.na-mic.org/Wiki/index.php/Slicer-IGT/GPU-IGT#Volume_Rendering_Techniques| new volume rendering techniques] for details.
  
 
</div>
 
</div>
Line 25: Line 28:
  
 
<h1>Approach, Plan </h1>
 
<h1>Approach, Plan </h1>
Our approach is described by the references below.  Our challenge is to build the ITK infrastructure (such as new ITK iterators) to support this algorithm. Our main purpose at the Project Week is to collaborate on new algorithms and clinical data to provide the best solutions for our DBP partners.
+
Discuss which further efforts have to be taken to get a better usability of volume rendering (How can mapping functions be edited more intuitive, what are good presets etc.)
 +
 
 +
What are essential features for volume rendering in Slicer.
 +
 
 +
What are difficulties, issues when using volume rendering in connection with other modules.
 +
 
 +
How should a different rendering, GUI for DTI, label maps and gray scale volumes look like.
 +
 
 +
Figure out how difficult it is to integrate CUDA or other rendering algorithms into VTK and Slicer.
 
</div>
 
</div>
  
Line 34: Line 45:
 
====June 2007 Project Week====
 
====June 2007 Project Week====
 
The work on this project started in August 2007.
 
The work on this project started in August 2007.
====Jan 2007 Project Half Week====
+
====Jan 2008 Project Half Week====
 
+
We added additional usability features, including a vtkBoxWidget and a GUI for volume rendering of labelmaps. We could also improve performance issues and are working on adding scene snapshot functionality.
  
 
</div>
 
</div>
Line 42: Line 53:
  
 
</div>
 
</div>
 
  
 
===References===
 
===References===

Latest revision as of 18:07, 10 July 2017

Home < 2008 Winter Project Week VolumeRendering
Volume Rendering, mapping functions optimized for lung
Edit clipping planes using vtkBoxWidget


Key Investigators

  • Isomics: Steve Pieper
  • SPL/IGT: Benjamin Grauer, Andreas Freudling

Objective

Integration of interactive volume rendering into Slicer 3 using hardware and software based rendering techniques.

Improve the existing framework using new algorithms / frameworks like CUDA or other rendering algorithms.

Use volume rendering for 4D IGT.

See integration of volume rendering in Slicer 3 and new volume rendering techniques for details.

Approach, Plan

Discuss which further efforts have to be taken to get a better usability of volume rendering (How can mapping functions be edited more intuitive, what are good presets etc.)

What are essential features for volume rendering in Slicer.

What are difficulties, issues when using volume rendering in connection with other modules.

How should a different rendering, GUI for DTI, label maps and gray scale volumes look like.

Figure out how difficult it is to integrate CUDA or other rendering algorithms into VTK and Slicer.

Progress

June 2007 Project Week

The work on this project started in August 2007.

Jan 2008 Project Half Week

We added additional usability features, including a vtkBoxWidget and a GUI for volume rendering of labelmaps. We could also improve performance issues and are working on adding scene snapshot functionality.


References