Difference between revisions of "2008 July Slicer IGT VV Link Session II"

From NAMIC Wiki
Jump to: navigation, search
Line 1: Line 1:
[[Image:BrainLab-BioImageSuite-Slicer.jpg|right|thumb=300px|Slicer Navigation Driven by Brain Lab Using Yale's Bioimage Suite to bridge VVLink to OpenIGTLink]]
 
  
 
Date: Wednesday, July 23
 
Date: Wednesday, July 23
  
 
Location: 1249 Boylston Street, Second Floor Conference Room. ([http://www.spl.harvard.edu/pages/Directions#Driving_Directions Driving directions to 1249 Boylston, Boston MA])
 
Location: 1249 Boylston Street, Second Floor Conference Room. ([http://www.spl.harvard.edu/pages/Directions#Driving_Directions Driving directions to 1249 Boylston, Boston MA])
 +
 +
[[Image:BrainLab-BioImageSuite-Slicer.jpg|right|300px|Slicer Navigation Driven by Brain Lab Using Yale's Bioimage Suite to bridge VVLink to OpenIGTLink]]
  
 
Hotel Information: [[Boston_Hotels]]
 
Hotel Information: [[Boston_Hotels]]

Revision as of 22:00, 23 July 2008

Home < 2008 July Slicer IGT VV Link Session II

Date: Wednesday, July 23

Location: 1249 Boylston Street, Second Floor Conference Room. (Driving directions to 1249 Boylston, Boston MA)

Slicer Navigation Driven by Brain Lab Using Yale's Bioimage Suite to bridge VVLink to OpenIGTLink

Hotel Information: Boston_Hotels

Participants:

  • Xenios Papademetis
  • Noby Hata
  • Haiying Liu
  • Junichi Tokuda
  • Steve Pieper
  • Tina Kapur
  • Lauren O'Donnell
  • Ron Kikinis

Schedule

Tuesday Afternoon:

Availability: Xenios at ~1:30pm, Steve, Haiying, Junichi

Wednesday:

Availability: Steve in afternoon, All day: Xenios, Haiying, Junichi

  • Continuation of Brainlab vvlink integration with Slicer
  • 2:30 journal club presentation by Xenios (at 1249)

Agenda

  • Steve suggested:
    • going through the vvlink and openigtlink protocols
      • identifying areas places where igtl can be expanded
      • finding gaps in vvlink that will need workaround (image orientation - Xenios has heuristics for this)
    • reviewing options for the vv/igtl proxy server
      • should this be on a stand alone machine?
      • do we make this proxy code into a project of it's own or part of igtl library
      • write any test code to move the vv/igtl proxy concept along (how can we use the demo from the project week as the basis for something that can be used clinically?)
    • Xenios feedback on igtl library software and use cases (he ended up using the C code and not the C++)
    • collect practical feedback on vvlink in the OR from Yale's experience
    • get demos of Yale software and discuss interoperability options and possible funding mechanisms.
  • Lauren O'Donnell from the BWH Neurosurgery Department can join on Tuesday afternoon to discuss what clinicians would like to see out of the system.

Referencees