Difference between revisions of "OpenIGTLink/Library2"
From NAMIC Wiki
(Created page with '=About OpenIGTLink Library version 2= The OpenIGTLink Library version 2 is being developed to support OpenIGTLink protocol version 2. To try some…') |
|||
Line 1: | Line 1: | ||
=About OpenIGTLink Library version 2= | =About OpenIGTLink Library version 2= | ||
The OpenIGTLink Library version 2 is being developed to support [[OpenIGTLink/ProtocolV2/Draft|OpenIGTLink protocol version 2]]. | The OpenIGTLink Library version 2 is being developed to support [[OpenIGTLink/ProtocolV2/Draft|OpenIGTLink protocol version 2]]. | ||
− | To try | + | To try the library version 2, please follow the instruction in [[OpenIGTLink/TryVersion2| the instruction to try version 2 protocol]] |
+ | |||
+ | =Testing= | ||
+ | The library version 2 will provide more comprehensive testing than version 1. Specifically, it will provide server-client communication tests, which are not available in version 1. | ||
+ | |||
+ | Xenios Papademitris suggested: | ||
+ | # Setting a ``server'' program that gets initialized at the start of the ctest process that simply accepts messages and dumps them to a file (with predefined filenames). Then you can compare what you sent with what it received. | ||
+ | # Having a multithreaded test where the server is on one thread and the client on another .... |
Revision as of 03:25, 16 August 2010
Home < OpenIGTLink < Library2About OpenIGTLink Library version 2
The OpenIGTLink Library version 2 is being developed to support OpenIGTLink protocol version 2. To try the library version 2, please follow the instruction in the instruction to try version 2 protocol
Testing
The library version 2 will provide more comprehensive testing than version 1. Specifically, it will provide server-client communication tests, which are not available in version 1.
Xenios Papademitris suggested:
- Setting a ``server program that gets initialized at the start of the ctest process that simply accepts messages and dumps them to a file (with predefined filenames). Then you can compare what you sent with what it received.
- Having a multithreaded test where the server is on one thread and the client on another ....