2010 Summer Project Week Breakout Session:OpenIGTLink

Back to 2010_Summer_Project_Week

Organizer: Junichi Tokuda
Date: Thursday, June 24, 2010
OpenIGTLink Home Page: OpenIGTLink

Agenda

• 9-10am: OpenIGTLink Updates and Next Steps
  • Summary of OpenIGTLink
  • Discussion on protocol version 2.
• 10a-12pm: Hands-on session.
  • Notes: Stealthlink Protocol (for reference)
• 12-1pm: Break for lunch
• 1-2pm: Demos of working OpenIGTLink based systems
  • AIST demos (TBD)
• 2-3pm: OpenIGTLink Library, 3D Slicer and other tools
• 3-4pm: Simulator Discussion

Suggestions for agenda from TCON:

• Tracker simulator (Haiying)
• General session on simulators (maybe there should be a general discussion on this)
• BrainLab VectorVision-Slicer integration using OpenIGTLink
• Suggestions for hands-on session
  • hello world type demo application
  • 5-10 minutes from each of the vendors on how they can use it?
  • compare OpenIGTLink with Steathlink protocol
  • hands-on help in WPI system up and running (Greg will confirm)
  • planning to interface aurora tracker with Slicer using OpenIGTLink (Tamas)
  • discussion about the implementation -- message queueing idea/transport layer (Patrick Georgetown, Steve to followup)
    • Comments from Patrick
      • For latest update on this, please refer to the CTK wiki: http://www.commontk.org/index.php/Documentation/Messaging
      • Suggestion: use Message Bus and Publisher/Subscriber design pattern for system integration
      • OpenIGTLink can be used to define the common message schema, and ZeroMQ can be used to handle the transportation layer abstraction
      • ZeroMQ is a small and fast implementation of the Advanced Message Queuing Protocol under the LGPL license
      • It supports both synchronous and asynchronous messaging mode
      • It supportsTCP, Multicast/PGM, Inter-process, and inter-thread transportation
      • CMake version of library can be found here http://github.com/PatrickCheng/zeromq2
      • API can be found here http://api.zeromq.org/zmq.html

---

Notes

Discussion on OpenIGTLink Protocol version 2

• Finalize version 2 protocol
  • Summary of version 2 protocol
  • New support for image-guided systems
    • Discussion on new commands is in progress.
  • Matlab integration
    • There have been several requests for Matlab OpenIGTLink interface.
    • Prototype Matlab/Octave interface is available.
    • New message type to support "remote procedure call"??
  • (Please put your agenda here)

Dissemination, collaboration etc.)

The following item is part of NCIGT. We need inputs from Ron and Tina.

• Tutorial (how we do now, and how it should be)
• web presence (how we are, and how it should be)
• Ctest (how we do)
• Use Slicer ML or dedicated ML?

Hands-on session (11am-12pm)

• Opportunity for IGT developers to consult with OpenIGTLink experts and find solutions for their project.

OpenIGTLink Library, 3D Slicer and other tools

• Features
• Message classes
• Example programs
• Timeline

---

Teleconference on May 27 (Thu) 3pm-

Objectives

• Topics to discuss during the event
• Finalize the schedule
• Action items

Participants

Dan Marcus, Misha Milchenko, Tina, Nicole, Jim, Steve, Lorent, Greg, Wendy, Andre, Xiaodong, Leslie Holton, Tamas, Ron, Dominik

Agenda

• Agenda in the project week
  • Summary of OpenIGTLink
    • Short presentation about overview and updates of OpenIGTLink for those who are not in the presentation on Tuesday.
  • Discussion on protocol version 2.
    • New features for 3D Slicer
    • Matlab
    • Messages for sensor data (proposed by AIST project)
    • Endoscope/camera control
  • Hands-on session. Specifics of this session will be decided after the May 27th tcon.
  • Demos of working OpenIGTLink based systems
  • OpenIGTLink Library, 3D Slicer and other tools
    • Matlab interfaces
    • 3D Slicer user interface
    • Tutorials

• Demos (please feel free to add)
  • IGSTK demo from Haiying
  • AIST demo (may be video)
  • New 3D Slicer OpenIGTLink IF

• Breakout session schedule
  • Make sure that all participants can sessions they need
  • Order of sessions

• Action items by Project Week
  • List all potential applications
  • List all problems, issues regrading the current protocol
  • Feedbacks