OpenIGTLink/ProtocolV2/Type/TrackingData - Revision history

Tokuda at 04:43, 30 November 2011

2011-11-30T04:43:26Z

Tokuda: /* STT_TDATA */

2010-11-30T21:34:41Z

STT_TDATA

Tokuda: /* RTS_TDATA */

2010-11-30T05:08:38Z

RTS_TDATA

Tokuda: /* TDATA */

2010-07-09T01:33:25Z

TDATA

Tokuda: /* TDATA */

2010-07-09T01:32:12Z

TDATA

Tokuda: /* TDATA */

2010-07-09T01:23:45Z

TDATA

Tokuda: /* TDATA */

2010-07-09T01:18:30Z

TDATA

Tokuda at 03:20, 1 July 2010

2010-07-01T03:20:53Z

Tokuda at 03:16, 1 July 2010

2010-07-01T03:16:03Z

Tokuda at 03:15, 1 July 2010

2010-07-01T03:15:26Z

← Older revision		Revision as of 04:43, 30 November 2011
Line 1:		Line 1:
−	[[OpenIGTLink/ProtocolV2/~~Draft~~ \| << Version 2 ~~Draft~~ Page]]	+	[[OpenIGTLink/ProtocolV2/Index \| << Version 2 Index Page]]

	=Summary=		=Summary=

@@ Line 75: / Line 75: @@
 |-
 | align="left" | Coordinate system name
-| align="left" | char[20]
+| align="left" | char[32]
 | align="left" | Coordinate system to use. Can be empty for default coordinate system. (not included if action = 2)
 |-
@@ Line 84: / Line 84: @@
 * Easy to develop. Sample pseudo code: '''while(true) { recv(trackingdata); updateView(trackingdata); }'''
 *Usually the tracking data will be sent using the standard coordinate system, which is also used for POINT, IMAGE, ... But this does only work after patient registration. Therefore the body of START_PUSH has an optional field for specifing the coordinate system "CAMERA". To switch back to the standard coordinate system, one has to send STOP_PUSH and afterwards START_PUSH without explicitly specifing the camera coordinate system.
 ==STP_TDATA==

← Older revision		Revision as of 05:08, 30 November 2010
Line 98:		Line 98:
	==RTS_TDATA==		==RTS_TDATA==

		+	{\| border="1" cellpadding="5" cellspacing="0" align="center"
		+	\|-
		+	\| align="left style="background:#e0e0e0;" \| Data
		+	\| align="left style="background:#e0e0e0;" \| Type
		+	\| align="left style="background:#e0e0e0;" \| Description
		+	\|-
		+	\| align="left" \| Status
		+	\| align="left" \| 8 bit unsigned
		+	\| align="left" \| 0: Success 1: Error
		+	\|-
		+	\|}

	=Implementations=		=Implementations=

@@ Line 31: / Line 31: @@
 | align="left" | 12 values like in TRANSFORM message
 |-
-| colspan=3 align="center" | ...
+| colspan=3 align="center" style="background:#f0f0f0;" | ...
 |-
 | align="left" | NAME_N

@@ Line 31: / Line 31: @@
 | align="left" | 12 values like in TRANSFORM message
 |-
-| align="left" style="background:#0F0F0F"| ...
+| colspan=3 align="center" | ...
 |-
 | align="left" | NAME_N

@@ Line 15: / Line 15: @@
 | align="left style="background:#e0e0e0;" | Description
 |-
-| align="left" | Name
+| align="left" | NAME_1
 | align="left" | char[20]
 | align="left" | Name (=Id) of the instrument/tracker
 |-
-| align="left" | Type
+| align="left" | TYPE_1
 | align="left" | 8 bit unsigned
 | align="left" | 1: tracker, 2: 6D instrument (regular instrument), 3: 3D instrument (only tip of the instrument defined), 4: 5D instrument (tip and handle are defined, but not the normal vector)
@@ Line 27: / Line 27: @@
 | align="left" | Reserved
 |-
-| align="left" | Matrix
+| align="left" | MATRIX_1
 | align="left" | 32 bit float
 | align="left" | 12 values like in TRANSFORM message

@@ Line 82: / Line 82: @@
 =Implementations=
-XXX message type is implemented in the following source code.
+The TDATA message type is implemented in the following source code.
-*igtlXXXXMessage.h (link to the file in subversion repository, if available)
+*[http://svn.na-mic.org/NAMICSandBox/trunk/OpenIGTLink/Source/igtlTrackingDataMessage.h igtlTrackingDataMessage.h]
-*igtlXXXXMessage.cxx (link to the file in subversion repository, if available)
+*[http://svn.na-mic.org/NAMICSandBox/trunk/OpenIGTLink/Source/igtlTrackingDataMessage.cxx igtlTrackingDataMessage.cxx]
 =Contributors=
-You may list names of contributors in this section.
+Alexander Schaal
 =Comments=
-==Comments==
 ''Junichi'':
 *How about adding 8- or 16-bit status field in TDATA? This will allow us to indicate that coordinate system is not registered. I would like to keep START_PUSH message simple....

← Older revision		Revision as of 03:16, 1 July 2010
Line 1:		Line 1:
−	[[OpenIGTLink/ProtocolV2/~~Proposals~~ \| << Version 2 Draft Page]]	+	[[OpenIGTLink/ProtocolV2/Draft \| << Version 2 Draft Page]]

	=Summary=		=Summary=

@@ Line 2: / Line 2: @@
 =Summary=
-The XXXX format supports blah-blah-blah.
+The TDATA message type is intended for transferring 3D positions of surgical tools, markers etc. Those positions are often measured by optical, electromagnetic or other type of 3D position sensor continuously and transferred as series of messages. Since it is important for software that receives TDATA to control data flow, STT_TDATA query data type has interval field to control the frame rate of consecutive messages.
 =Message Types=
-==XXXX==
+==TDATA==
 {| border="1" cellpadding="5" cellspacing="0" align="center"
@@ Line 13: / Line 15: @@
 | align="left style="background:#e0e0e0;" | Description
 |-
-| align="left" | V1
+| align="left" | Name
-| align="left" | unsigned short
+| align="left" | char[20]
-| align="left" | Value 1
+| align="left" | Name (=Id) of the instrument/tracker
 |-
-| align="left" | V2
+| align="left" | --
-| align="left" | 8bit unsigned int
+| align="left" | 8 bit unsigned
-| align="left" | Value 2
+| align="left" | Reserved
 |-
-| align="left" | ...
+| align="left" | Matrix
-| align="left" | ...
+| align="left" | 32 bit float
-| align="left" | ...
+| align="left" | 12 values like in TRANSFORM message
 |-
 |}
 {| border="1" cellpadding="5" cellspacing="0" align="center"
 |-
@@ Line 34: / Line 40: @@
 | align="left style="background:#e0e0e0;" | Type
 | align="left style="background:#e0e0e0;" | Description
 |-
 |}
-==STT_XXXX==
+==STT_TDATA==
 {| border="1" cellpadding="5" cellspacing="0" align="center"
@@ Line 58: / Line 52: @@
 | align="left style="background:#e0e0e0;" | Description
 |-
-| align="left" | V1
+| align="left" | Resolution
-| align="left" | unsigned short
+| align="left" | 32 bit unsigned
-| align="left" | Value 1
+| align="left" | Minimum time between two frames. Use 0 for as fast as possible. If e.g. 50 ms is specified, the maximum update rate will be 20 Hz.
 |-
-| align="left" | ...
+| align="left" | Coordinate system name
-| align="left" | ...
+| align="left" | char[20]
-| align="left" | ...
+| align="left" | Coordinate system to use. Can be empty for default coordinate system. (not included if action = 2)
 |-
 |}
-==STP_XXXX==
+* All tracking data from one frame is included.
 {| border="1" cellpadding="5" cellspacing="0" align="center"
@@ Line 80: / Line 75: @@
 | align="left style="background:#e0e0e0;" | Type
 | align="left style="background:#e0e0e0;" | Description
 |-
 |}
 =Implementations=
@@ Line 104: / Line 90: @@
 =Comments=
-People in the community may put comments here.
+==Comments==