TubeTK/OpenIGTLink: Difference between revisions

From KitwarePublic
Jump to navigationJump to search
Line 20: Line 20:


== Types of OpenIGTLink message ==
== Types of OpenIGTLink message ==
=== Implementation ===


=== Version 1 ===
=== Version 1 ===
http://svn.na-mic.org/NAMICSandBox/trunk/OpenIGTLink
# Transform  ( igtlTransformMessage )
# Transform  ( igtlTransformMessage )
# Image      ( igtlImageMessage )
# Image      ( igtlImageMessage )
Line 27: Line 33:
# Status message ( igtlStatusMessage )
# Status message ( igtlStatusMessage )
=== Version 2 ===
=== Version 2 ===
http://svn.na-mic.org/NAMICSandBox/trunk/OpenIGTLink2_beta/


= OpenIGTLink CLI Application in TubeTK=
= OpenIGTLink CLI Application in TubeTK=

Revision as of 15:57, 4 June 2010

Introduction

OpenIGTLink is a communication protocol designed to work on the TCP/IP application layer to handle image, tracking data, transform, device control and monitoring command, and other user-defined data types. Example usecases

  1. A computer running IGSTK based navigation application and a computer running Slicer are connected using a network cable. The IGSTK application gathers pose information of surgical instruments and packages them in OpenIGTLink message format and then sends the data over network connection using OpenIGTLink protocol to the computer running Slicer for visualization and/or further processing
  2. A computer running tubetk based vessel segmentation application is connected to the BrainLab VectorVision machine. VectorVisison fetches Ultrasound images, packages them as OpenIGTLink image message and sends it to the computer running the tubetk application.

Description

Workflow

Client

  1. Establish connection with server side ( Example: igtl::ClientSocket )
  2. Generate OpenIGTLink message (data-to-be-sent ) and package in Open IGT Link format. (Example: igtl::TransformMessage )
  3. Send data through TCP/IP socket connection

Server side

  1. Create a server socket and wait for the client to connect ( igtlServerSocket )
  2. When connection is established with a client, get into a "Ready" state to start receiving messages.
  3. When a message is received, error check and unpack the header and identify the message type and prepare to receive the message body
  4. Receive, error check, unpack and parse the message body according to the message type.

Types of OpenIGTLink message

Implementation

Version 1

http://svn.na-mic.org/NAMICSandBox/trunk/OpenIGTLink

  1. Transform ( igtlTransformMessage )
  2. Image ( igtlImageMessage )
  3. Position ( igtlPositionMessage )
  4. Status message ( igtlStatusMessage )

Version 2

http://svn.na-mic.org/NAMICSandBox/trunk/OpenIGTLink2_beta/

OpenIGTLink CLI Application in TubeTK

Reference

  1. NAMIC OpenIGTLink wiki page