Difference between revisions of "OpenIGTLink/Library/Discussions"
From NAMIC Wiki
| Line 18: | Line 18: | ||
** con | ** con | ||
*** size | *** size | ||
| − | *** | + | *** needs interpreter. impossible to record unknown type message. |
==Architecture== | ==Architecture== | ||
| Line 28: | Line 28: | ||
** not implemented in the OpenIGTLink library | ** not implemented in the OpenIGTLink library | ||
** can be implemented as a single-thread program | ** can be implemented as a single-thread program | ||
| + | |||
| + | ==Logistics== | ||
| + | *Make a copy repository of OpenIGTLink library | ||
| + | |||
| + | |||
| + | ==Skills required== | ||
| + | *Basic knowledge about [OpenIGTLink | OpenIGTLink]. | ||
| + | *Socket programming | ||
| + | *Thread | ||
| + | *SVN, CMake | ||
Revision as of 04:03, 7 October 2008
Home < OpenIGTLink < Library < Discussions[OpenIGTLink | << OpenIGTLink]]
Open IGT Link protocol description
Log function
Data file format
- dump message data to the file
- pro
- can be used for any type of data
- easy to replay
- con
- too redundant, if the data source does not change
- needs reader software
- pro
- text format
- pro
- human readable
- con
- size
- needs interpreter. impossible to record unknown type message.
- pro
Architecture
- 1-port, 1-connection
- needs threading
- implemented in the OpenIGTLink libary
- 1-port, multiple connection
- use 'select()' function
- not implemented in the OpenIGTLink library
- can be implemented as a single-thread program
Logistics
- Make a copy repository of OpenIGTLink library
Skills required
- Basic knowledge about [OpenIGTLink | OpenIGTLink].
- Socket programming
- Thread
- SVN, CMake
