OpenIGTLink/ProtocolV2/Summary - Revision history

Tokuda at 18:09, 12 December 2011

2011-12-12T18:09:19Z

Tokuda at 18:09, 12 December 2011

2011-12-12T18:09:05Z

Tokuda at 18:08, 12 December 2011

2011-12-12T18:08:52Z

Tokuda: /* New message types */

2010-05-20T14:37:30Z

New message types

Tokuda: /* Messages for image-guided systems(TBD) */

2010-05-20T13:38:24Z

Messages for image-guided systems(TBD)

Tokuda: /* Overview */

2010-05-20T13:14:47Z

Overview

Tokuda at 13:13, 20 May 2010

2010-05-20T13:13:27Z

Tokuda at 13:04, 20 May 2010

2010-05-20T13:04:43Z

Tokuda at 13:03, 20 May 2010

2010-05-20T13:03:03Z

Tokuda: /* New message types */

2010-05-20T12:54:18Z

New message types

← Older revision		Revision as of 18:09, 12 December 2011
Line 1:		Line 1:
−	[[ProtocolV2/Index \| << OpenIGTLink Version 2]]	+	[[OpenIGTLink/ProtocolV2/Index \| << OpenIGTLink Version 2]]

	=Overview=		=Overview=

← Older revision		Revision as of 18:09, 12 December 2011
Line 1:		Line 1:
−	[[ProtocolV2/Index \| << OpenIGTLink]]	+	[[ProtocolV2/Index \| << OpenIGTLink Version 2]]

	=Overview=		=Overview=

← Older revision		Revision as of 18:08, 12 December 2011
Line 1:		Line 1:
−	[[~~OpenIGTLink~~ \| << OpenIGTLink]]	+	[[ProtocolV2/Index \| << OpenIGTLink]]

	=Overview=		=Overview=

@@ Line 20: / Line 20: @@
 The following tables show lists of message types available in version 2.
-==Messages for image-guided systems(TBD)==
+==New Messages for image-guided systems(TBD)==
 {|border="1" cellpadding="1"
 | style="width:10%; background:#88A8FF"|Type name
@@ Line 66: / Line 66: @@
 |}
-==Messages for general applications (TBD)==
+==New Messages for general applications (TBD)==
 {|border="1" cellpadding="1"
 | style="width:10%; background:#88A8FF"|Type name

@@ Line 41: / Line 41: @@
 ||--
 ||RTS_IMGMETA
-|align=left|List of images including patient name, ID (medical record number), size, etc.
+|align=left|List of image meta data including patient name, ID (medical record number), size, etc.
 |-
 |style="width:25%; background:#F0F8FF"| LBMETA
@@ Line 48: / Line 48: @@
 ||--
 ||RTS_LBMETA
-|align=left|List of label data.
+|align=left|List of label meta data.
 |-
 |style="width:25%; background:#F0F8FF"| POINT

@@ Line 4: / Line 4: @@
 The OpenIGTLink Protocol is ideal for building a research prototype system, because of its simple and standardized specification that requires less effort on design and development of communication mechanism for systems integration. By using OpenIGTLink, developers can save their time for more essential part of research. The OpenIGTLink's simple specification has been well accepted by the community, resulting a number of applications in the IGT research community, since it's initial release in early 2008.
-While we keep the protocol as simple as possible, it is also important to support as many IGT devices as possible to maximize the connectivity among software and devices, which potentially frees the developers from tedious works for system integration. There have been a number of feature requests that would benefit many IGT research projects, such as connectivity with commercial products, and connectivity with other major research tools, such as MATLAB. To respond to those request, and to increase the number of potential applications, we decided review the requests and release version 2 protocol during NA-MIC Summer Project Week 2010. The new protocol defines a set of new message types with new querying scheme, while maintaining a backward compatibility with version 1. This page summarizes the features in version 2.
+While we keep the protocol as simple as possible, it is also important to support as many IGT devices as possible to maximize the connectivity among software and devices, which potentially frees the developers from tedious coding just for system integration. There have been a number of feature requests that would benefit many IGT research projects, such as connectivity with commercial products, and connectivity with other major research tools, such as MATLAB. To respond to those request, and to increase the number of potential applications, we decided review the requests and release version 2 protocol during NA-MIC Summer Project Week 2010. The new protocol defines a set of new message types with new querying scheme, while maintaining a backward compatibility with version 1. This page summarizes the features in version 2.
 =Simple Query Scheme=

@@ Line 2: / Line 2: @@
 =Overview=
-The OpenIGTLink Protocol is ideal for building a research prototype system, because of its simple and standardized specification that requires less effort of developers on design and development of communication mechanism for systems integration. By using OpenIGTLink, developers can save their time for more essential part of research. The OpenIGTLink's simple specification has been well accepted by the community, resulting a number of applications in the IGT research community, since it's initial release in early 2008.
+The OpenIGTLink Protocol is ideal for building a research prototype system, because of its simple and standardized specification that requires less effort on design and development of communication mechanism for systems integration. By using OpenIGTLink, developers can save their time for more essential part of research. The OpenIGTLink's simple specification has been well accepted by the community, resulting a number of applications in the IGT research community, since it's initial release in early 2008.
 While we keep the protocol as simple as possible, there have also been a number of feature requests that would benefit many IGT research projects, such as connectivity with commercial products, and connectivity with other major research tools, such as MATLAB. To respond to those request, and to increase the number of potential applications, we decided review the requests and release version 2 protocol during NA-MIC Summer Project Week 2010. The new protocol defines a set of new message types with new querying scheme, while maintaining a backward compatibility with version 1. This page summarizes the features in version 2.

← Older revision		Revision as of 13:03, 20 May 2010
Line 1:		Line 1:
		+	[[OpenIGTLink \| << OpenIGTLink]]
		+
	=Overview=		=Overview=
	The OpenIGTLink Protocol is ideal for building a research prototype system, because of its simple and standardized specification that requires less effort of developers on design and development of communication mechanism for systems integration. By using OpenIGTLink, developers can save their time for more essential part of research. The OpenIGTLink's simple specification has been well accepted by the community, resulting a number of applications in the IGT research community, since it's initial release in early 2008.		The OpenIGTLink Protocol is ideal for building a research prototype system, because of its simple and standardized specification that requires less effort of developers on design and development of communication mechanism for systems integration. By using OpenIGTLink, developers can save their time for more essential part of research. The OpenIGTLink's simple specification has been well accepted by the community, resulting a number of applications in the IGT research community, since it's initial release in early 2008.

@@ Line 78: / Line 78: @@
 ||--
 ||RTS_REXEC
-|align=left|Remote procedure execution
+|align=left|Remote procedure execution. In most case, the REXEC type is issued as a query (GET_REXEC) and obtain a RTS_REXEC message that contains a list of result data.
 |-
-|style="width:25%; background:#F0F8FF"| IMGMETA
+|style="width:25%; background:#F0F8FF"| AARRAY
-||GET_IMGMETA
+||GET_AARRAY
-||--
+||STT_AARRAY
-||--
+||STP_AARRAY
-||RTS_IMGMETA
+||RTS_AARRAY
-|align=left|List of images including patient name, ID (medical record number), size, etc.
+|align=left|Associative array to transfer a set of values with key names.
 |-
 |}