Difference between revisions of "Slicer/Features/Middleware"
From NAMIC Wiki
| Line 22: | Line 22: | ||
* Priority | * Priority | ||
* Point - multi-point data transfer | * Point - multi-point data transfer | ||
| + | |||
| + | Question | ||
| + | * UDP - fast, no delay due to ACK packages | ||
| + | * TCP/IP - reliable, easy | ||
See: [http://www.cisst.org/wiki/MRI_robot/MIT_2007_06_27_Meeting discussion about data transfer] | See: [http://www.cisst.org/wiki/MRI_robot/MIT_2007_06_27_Meeting discussion about data transfer] | ||
Revision as of 15:16, 14 December 2007
Home < Slicer < Features < MiddlewareContents
Title
Middleware
Names
- session leader
- participants
Technology/Function description
- Publish subscribe ORB/ACE [Peter]
- Socket IGSTK [Junichi Patrick]
Requirements
- Reliable for command transfer (all data transferred, in order)
- Fast for tracking data transfer (only the latest coordinate is required, can lose data)
- Image transfer (500K or more)
- Data types (struct: string, integer, float)
- Data type checking (number is correctly formatted etc)
- Time out (device is down)
Would be nice to have
- Priority
- Point - multi-point data transfer
Question
- UDP - fast, no delay due to ACK packages
- TCP/IP - reliable, easy
See: discussion about data transfer
Potential application in IGT
- Tracker data transfer
- Image transfer from MRI
- Robot coordinate transfer
- Robot control
- Periferials: OpenTracker/Navitrack has 3D mouse driver etc.
