Difference between revisions of "OpenIGTLink/Slicer"
| Line 21: | Line 21: | ||
For Slicer 3.2, please see [[OpenIGTLink/Slicer_3_2| old page]]. | For Slicer 3.2, please see [[OpenIGTLink/Slicer_3_2| old page]]. | ||
| − | == | + | ==From source== |
Building instruction can be found in [[OpenIGTLink/Slicer/Build]]. | Building instruction can be found in [[OpenIGTLink/Slicer/Build]]. | ||
Revision as of 17:49, 3 December 2008
Home < OpenIGTLink < SlicerContents
Overview
The 3D Slicer OpenIGTLink Interface Module is a program module for that can handle network communications between 3D Slicer and external software / hardware using OpenIGTLink protocol. The module provides following functions:
- Data import: The module can import position, linear transform and image data from OpenIGTLink-compliant software / hardware to the MRML scene.
- Data export: The module can export linear transform and image data from the MRML scene.
- Multi-connection: The module can manage multiple OpenIGTLink connections at the same time.
- Locator visualization: The user can choose one of linear transforms in the MRML scene to visualize its position and orientation in the 3D space.
- Slice driving: The module can control volume re-slicing plane based on linear transform in the MRML scene.
Install the Software
From binaries
The module is available only in Slicer 3.3 source distribution. For Slicer 3.2, please see old page.
From source
Building instruction can be found in OpenIGTLink/Slicer/Build.
Install Tracker Simulator to Testing the OpenIGTlink interface module
To test the OpenIGTLink interface module (or other OpenIGTLinkcomplaint devices and software), tracking simulator software is provided as an example program of the OpenIGTLink library (note that the OpenIGTLink library is different from the OpenIGTLink interface module in 3D Slicer).
From binaries
Obtain a binary file for your environment.
- For Linux (x86, 32-bit).
- For Linux (x86, 64-bit).
- For Windows (32-bit).
- For Mac OS X (x86).
- For Mac OS X (PPC).
From Source
The instruction can be found in OpenIGTLink/Library/Build. Please make sure that you enable "build examples" option.
Testing Open IGT Link Module -- Show Tracking Device in the 3D Space
Set up Open IGT Link Module
- Select "OpenIGTLinkIF" from "Modules:" menu
- Open "Connector Browser" frame, and press "Add" button below the "Connectors" list to add a new connector
- Configure and start the connector. Choose "Server" check box in the "Type" option, then clinck "Active" check box. Now the Slicer is ready to accept connections through Open IGT Link.
Run Tracker Simulator
Go to OpenIGTLink binary directory.
$ cd <path to OpenIGTLink-build>/bin
To send dummy coordinate data to the Slicer running on localhost with frame rate of 10 fps, run:
$ ./TrackerClient localhost 18944 10
Visualize Tracker Position
To see the coordinate from the Tracker Simulator,
- Open "Visualization / Slice Control" frame in the OpenIGTLink module interface.
- Choose "Tracker (LinearTransform) from Locator Source menu in Locator Display frame.
- Click the "Show Locator" check button. A locator model shows up on the 3D viewer.
Architecture
Overview
The OpenIGTLink Interface module is designed to adapt to the 3D Slicer’s scene graph mechanism called Medical Reality Modeling Language (MRML) architecture. MRML provides a unified way to handle various kinds of data including images, transforms, and models in the IGT setting as MRML nodes. In order to manage multiple nodes, all MRML nodes have a tree structure. For example, the user can apply a transform to an image by placing it under the transform node as a child node. When the OpenIGTLink module receives an OpenIGTLink message, it creates a MRML node with the same name as the "device name" in the message and imports the data to the node. If a node with the same name and data type already exists, the module simply updates the data. The module also can export the data from a MRML node through the OpenIGTLink interface. This mechanism maximizes the flexibility to import/export data to/from the 3D Slicer, since users can configure the MRML node tree interactively without changing the source code of the software. In addition, this mechanism make it easy for other software modules to exchange data with external software or hardware through OpenIGTLink.
Connectors
To manage multiple OpenIGTLink communications simultaneously, the OpenIGTLink Interface module handles an OpenIGTLink connection as a "connector". One connector can establish connection with only one external hardware / software to exchange data, and the user can add connectors from the graphical user interface (GUI) as much as he/she need. Each connector can be configured as either TCP/IP server or client independently. Note that this does not mean directions of data stream; it just determines whether the module or the external software / hardware waits for (listens to) the other side to initiate the connection. Once the connection is established, there is no difference between server and client connectors.
The figure bellow shows an example schematic diagram where multiple devices are communicating with the 3D Slicer through the OpenIGTLink Interface. Each connector serves as an interface between external device and MRML scene to convert OpenIGTLink message to MRML node or vice versa.
From the developers' point of view, a connector is handled as an instance of vtkIGTLConnector class, which is defined in Modules/OpenIGTLinkIF/vtkIGTLConnector.cxx and vtkIGTLConnectors.h. Each instance has a thread to monitor communication with an external hardware / software.
Event-driven
The OpenIGTLink Interface module is driven by two types of events: arrivals of OpenIGTLink messages and update events in MRML scene. The module monitors incoming messages, and once it receives a message, it starts deserialization process to import the data into MRML scene as a MRML node. Other software modules in 3D Slicer can recognize that the data is imported into the MRML scene by catching the MRML event. The module also monitors events from MRML nodes, which the user has registered as nodes to export. When one of the nodes is updated from somewhere in the 3D Slicer, the module catches the update event and start serializing the data into OpenIGTLink message. the serialized data is transfered to the device through OpenIGTLink connection. This event-driven architecture allows other software modules in the 3D Slicer to exchange various kinds of data with external hardware and software without accessing API of OpenIGTLink interface (in other words, with few modification of the codes).
Loadmap
