Difference between revisions of "Plug-In 3D Viewer based on XIP"

From NAMIC Wiki
Jump to: navigation, search
 
(10 intermediate revisions by 2 users not shown)
Line 2: Line 2:
 
<gallery>
 
<gallery>
 
Image:PW2009-v3.png|[[2009_Summer_Project_Week|Project Week Main Page]]
 
Image:PW2009-v3.png|[[2009_Summer_Project_Week|Project Week Main Page]]
 +
Image:Xipexample.jpg|[http://openxip.org/ XIP: eXtensible Imaging Platform]
 +
Image:SlicerImage_lut_1.jpg|Volume Rendering in Slicer using XIP
 
</gallery>
 
</gallery>
  
 
==Key Investigators==
 
==Key Investigators==
 
* Siemens Corporate Research: Lining Yang, Melanie Grebe
 
* Siemens Corporate Research: Lining Yang, Melanie Grebe
 +
* Steve Pieper
  
 
<div style="margin: 20px;">
 
<div style="margin: 20px;">
Line 17: Line 20:
 
<div style="width: 27%; float: left; padding-right: 3%;">
 
<div style="width: 27%; float: left; padding-right: 3%;">
  
<h3>Our Approach, Plan</h3>
+
<h3>Our Approach and Plan</h3>
  
 
We will implement a Host/Plug-in interface API that leverages the use of XIP modules (based on Open Inventor), and as a first example we will implement a simple 3D Viewer that can load and display DICOM data and visualize/navigate it using 3 synchronized MPR windows and a 3D volume rendering window, with the ability to render fused MR brain data.
 
We will implement a Host/Plug-in interface API that leverages the use of XIP modules (based on Open Inventor), and as a first example we will implement a simple 3D Viewer that can load and display DICOM data and visualize/navigate it using 3 synchronized MPR windows and a 3D volume rendering window, with the ability to render fused MR brain data.
Line 26: Line 29:
  
 
<h3>Our Progress</h3>
 
<h3>Our Progress</h3>
We will bring a rough prototype and resolve pending issues during Project Week.
+
We implemented a prototype that directly embedded the XIP in the existing Volume Rendering Module of the 3D Slicer where we take the output volume and other parameters from Slicer/VTK and use them to build and render an XIP scenegraph using XIP's volume rendering nodes.
 +
 
 +
Future work:
 +
During the week we talked to Ron, Steve, Jim and many others to explore other ways of integrating the XIP and 3D Slicer. Among them are: (1) Uses the socket connection / Slicer Daemon to establish a host/plug-in architecture where we can leverage the strength of both the XIP/slicer world. One example is that XIP serves as a Dicom explorer host and slicer as a post-processing plugin. (2) Uses XIP to help the users to further process / perform visual programming of for example the slicer command line module results.
  
  

Latest revision as of 13:55, 25 June 2009

Home < Plug-In 3D Viewer based on XIP

Key Investigators

  • Siemens Corporate Research: Lining Yang, Melanie Grebe
  • Steve Pieper

Our Objective

Our objective is to create a new 3D Slicer Plug-in based on NCI's eXtensible Imaging Platform (XIP), which can then be used as a starting point for future projects involving NA-MIC and caBIG.

Our Approach and Plan

We will implement a Host/Plug-in interface API that leverages the use of XIP modules (based on Open Inventor), and as a first example we will implement a simple 3D Viewer that can load and display DICOM data and visualize/navigate it using 3 synchronized MPR windows and a 3D volume rendering window, with the ability to render fused MR brain data.

Our Progress

We implemented a prototype that directly embedded the XIP in the existing Volume Rendering Module of the 3D Slicer where we take the output volume and other parameters from Slicer/VTK and use them to build and render an XIP scenegraph using XIP's volume rendering nodes.

Future work: During the week we talked to Ron, Steve, Jim and many others to explore other ways of integrating the XIP and 3D Slicer. Among them are: (1) Uses the socket connection / Slicer Daemon to establish a host/plug-in architecture where we can leverage the strength of both the XIP/slicer world. One example is that XIP serves as a Dicom explorer host and slicer as a post-processing plugin. (2) Uses XIP to help the users to further process / perform visual programming of for example the slicer command line module results.