Difference between revisions of "Slicer3:VisualBlog"

From Slicer Wiki
Jump to: navigation, search
Line 5: Line 5:
 
Image:Cardioseg+volume.png|'''Cardiac segmentation and CT Volume Rendering, February 2008'''<br> Using data and segmentations from the [http://wiki.na-mic.org/Wiki/index.php/NA-MIC_Childrens_Collaboration collaboration with Boston Children's Hospital Pediatric Cardiology].
 
Image:Cardioseg+volume.png|'''Cardiac segmentation and CT Volume Rendering, February 2008'''<br> Using data and segmentations from the [http://wiki.na-mic.org/Wiki/index.php/NA-MIC_Childrens_Collaboration collaboration with Boston Children's Hospital Pediatric Cardiology].
 
Image:Slicer_IGTL_PartialImage.png|'''Partial image update using OpenIGTLink, February 2008'''<br> [http://wiki.na-mic.org/Wiki/index.php/OpenIGTLink OpenIGTLink] allows an external imaging scanner (Ultrasound/CT/MR) to update part of a volume, which has already been loaded on the Slicer. This is helpful if the imaging plane sweeps the subject, and images are transfered to the Slicer on-the-fly.
 
Image:Slicer_IGTL_PartialImage.png|'''Partial image update using OpenIGTLink, February 2008'''<br> [http://wiki.na-mic.org/Wiki/index.php/OpenIGTLink OpenIGTLink] allows an external imaging scanner (Ultrasound/CT/MR) to update part of a volume, which has already been loaded on the Slicer. This is helpful if the imaging plane sweeps the subject, and images are transfered to the Slicer on-the-fly.
Image:Slicer_CudaHead.jpg|'''The First MRML node rendering using CUDA February 2008'''<br> [http://wiki.na-mic.org/Wiki/index.php/Slicer3:Volume_Rendering_With_Cuda Cuda Volume Rendering] provides a Volume Rendering Method on the new and advanced NVidia Hardware.
+
Image:Slicer_CudaHead.jpg|'''The First MRML node rendering using CUDA February 2008'''<br> [[Slicer3:Volume_Rendering_With_Cuda| Cuda Volume Rendering]] provides a Volume Rendering Method on the new and advanced NVidia Hardware.
 
Image:Slicer_OpenIGTLINK.png|'''The First Implementation of OpenIGTLink, January 2008'''<br> [http://wiki.na-mic.org/Wiki/index.php/OpenIGTLink OpenIGTLink] protocol provides plug-and-play connectivity to tracking devices, imagers (MR, ultrasound ...) and other medical devices.  A real-time image transfer to the Slicer in 10 fps is demonstrated in the screenshot.
 
Image:Slicer_OpenIGTLINK.png|'''The First Implementation of OpenIGTLink, January 2008'''<br> [http://wiki.na-mic.org/Wiki/index.php/OpenIGTLink OpenIGTLink] protocol provides plug-and-play connectivity to tracking devices, imagers (MR, ultrasound ...) and other medical devices.  A real-time image transfer to the Slicer in 10 fps is demonstrated in the screenshot.
 
Image:Slicer_TrackerDaemon_IGSTK.png|'''Image from Haiying Liu, Patrick Cheng, Noby Hata, Junichi Tokuda, Luis Ibanez, and Steve Pieper, January 2008.''' <br>In the NAMIC All Hands Meeting 2008, the bi-directional socket communication has been established between the Tracker Daemon in Slicer 3 and IGSTK server which acquires tracking data from device and sends it to Tracker Daemon. The speed of communication is controlled by Slicer.
 
Image:Slicer_TrackerDaemon_IGSTK.png|'''Image from Haiying Liu, Patrick Cheng, Noby Hata, Junichi Tokuda, Luis Ibanez, and Steve Pieper, January 2008.''' <br>In the NAMIC All Hands Meeting 2008, the bi-directional socket communication has been established between the Tracker Daemon in Slicer 3 and IGSTK server which acquires tracking data from device and sends it to Tracker Daemon. The speed of communication is controlled by Slicer.

Revision as of 21:27, 8 April 2008

Home < Slicer3:VisualBlog




About the VisualBlog

The VisualBlog is meant to be an easy place to upload screenshot so that both developers and outside observes can track the progress of the project.

Many thanks to developers and users for contributing their images here.