Difference between revisions of "Slicer3:VisualBlog"
Line 2: | Line 2: | ||
<gallery caption="2008" widths="200px" perrow="4"> | <gallery caption="2008" widths="200px" perrow="4"> | ||
− | Image:Slicer_IGTL_PartialImage.png|'''Partial image update using OpenIGTLink, February 2008'''<br> [[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 | + | Image:Slicer_IGTL_PartialImage.png|'''Partial image update using OpenIGTLink, February 2008'''<br> [[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> [[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> [[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> [[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. |
Revision as of 20:15, 11 February 2008
Home < Slicer3:VisualBlog
Partial image update using OpenIGTLink, February 2008
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.The First MRML node rendering using CUDA February 2008
Cuda Volume Rendering provides a Volume Rendering Method on the new and advanced NVidia Hardware.The First Implementation of OpenIGTLink, January 2008
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 from Haiying Liu, Patrick Cheng, Noby Hata, Junichi Tokuda, Luis Ibanez, and Steve Pieper, January 2008.
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 from Steve Pieper, Luis Ibanez, Haiying Liu December 2007
Result of Slicer for IGT workshop showing Slicer3 transform node being updated by a IGSTK tracker process.Image from Steve Pieper, December 2007
Display of segmented heart data results using volume rendering inside Slicer3. See JHU Computational Anatomy Portal] for more information.Image from Tri Ngo and Steve Pieper, November 2007
Display of Stochastic Tractography results using volume rendering inside Slicer3. See here for more information.Image from Andy Freudling on October 2007
First results of volume rendering inside Slicer3. See here for more information.Image from Dirk, Matthew, Jim, and Steve on Monday, August 13, 2007
A new label map smoothing tool has been added to help with our collaboration with Children's Hospital Boston, SCI at University of Utah and Northeastern University. The unfiltered labelmap is shown in blue, and the filtered results are shown in peach.Image from Brad and Kilian on Wednesday, June, 21, 2007
Example of EMSegmenter in Slicer3Image from pieper on Friday, June, 9, 2007
Slicer3 Module for Stochastic Tractography from MIT (Ngo, Golland) and BWH (Westin, Kubicki).
Image from wjp on Friday, December 29, 2006 at 3:23PM
Module choose and navigation functionality integrated into the application toolbar to create more space for module GUIs on the side panel. Slice Controller widgets also updated to have more functionality available, a button to link and unlink their control, and an improved visual design.Image from pieper on Tuesday, August 08, 2006 at 4:26PM
A number of things have come together to allow the new prototype editor module. More ...Image from pieper on Thursday, July 27, 2006 at 5:21PM
Shows that a single pixel voxel in black is exactly bounded by a unit cube in RAS space. Also the blinking eye buttons for slice visiblility are hooked up and there is now a red-yellow-green color coding for the slice windows (carried over from slicer2).Image from pieper on Thursday, July 13, 2006 at 4:49PM
Test of interactive slice textured plane control. Not yet eneabled through GUI, but driven by a test script that you can source into the console. More ...Image from pieper on Monday, July 03, 2006 at 3:35PM
Test of the new logo widget for adding module-specific watermark logos directly in the 3d view. Uses a vtkLogoWidget from VTK cvs head. Kitware is working on cmake support to notify developers when a VTK cvs update is needed. Once that is done, the logo code will be added to slicer3 svn.
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.