Difference between revisions of "OpenIGTLink/ProtocolV2/Type/Point"
From NAMIC Wiki
(Created page with ' << Version 2 Draft Page =Summary= The XXXX format supports blah-blah-blah. =Message Types= ==XXXX== {| border="1" cellpadding="5" …') |
|||
Line 2: | Line 2: | ||
=Summary= | =Summary= | ||
− | The | + | The POINT message type is designed to transfer information about fiducials, which are often used in surgical planning and navigation in the image-guided therapy. |
=Message Types= | =Message Types= | ||
− | == | + | ==POINT== |
{| border="1" cellpadding="5" cellspacing="0" align="center" | {| border="1" cellpadding="5" cellspacing="0" align="center" | ||
Line 13: | Line 13: | ||
| align="left style="background:#e0e0e0;" | Description | | align="left style="background:#e0e0e0;" | Description | ||
|- | |- | ||
− | | align="left" | | + | | align="left" | Name |
− | | align="left" | | + | | align="left" | char[64] |
− | | align="left" | | + | | align="left" | Name or description of the point |
|- | |- | ||
− | | align="left" | | + | | align="left" | Group name |
− | | align="left" | | + | | align="left" | char[32] |
− | | align="left" | | + | | align="left" | Can be "Labeled Point", "Landmark", "Fiducal", ... |
|- | |- | ||
− | | align="left" | | + | | align="left" | R,G,B,A |
− | | align="left" | | + | | align="left" | 8 bit unsigned |
− | | align="left" | | + | | align="left" | Color in RGBA |
|- | |- | ||
− | | | + | | align="left" | X,Y,Z |
− | + | | align="left" | 32 bit float | |
− | + | | align="left" | Coordinate of the point | |
− | |||
− | |||
|- | |- | ||
− | | align="left | + | | align="left" | Diameter |
− | | align="left | + | | align="left" | 32 bit float |
− | | align="left | + | | align="left" | Diameter of the point, can be 0. |
|- | |- | ||
− | | align="left" | | + | | align="left" | Owner image |
− | | align="left" | | + | | align="left" | char[20] |
− | | align="left" | | + | | align="left" | Id of the owner image/sliceset. Points from different slicesets can be sent if slicesets are fused. |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|- | |- | ||
|} | |} | ||
− | + | ==GET_POINT== | |
− | == | ||
− | |||
{| border="1" cellpadding="5" cellspacing="0" align="center" | {| border="1" cellpadding="5" cellspacing="0" align="center" | ||
|- | |- | ||
Line 57: | Line 45: | ||
| align="left style="background:#e0e0e0;" | Type | | align="left style="background:#e0e0e0;" | Type | ||
| align="left style="background:#e0e0e0;" | Description | | align="left style="background:#e0e0e0;" | Description | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
|- | |- | ||
|} | |} | ||
− | |||
+ | ==STT_POINT== | ||
+ | |||
+ | N / A | ||
+ | |||
+ | ==STP_POINT== | ||
− | + | N / A | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
=Implementations= | =Implementations= |
Revision as of 02:59, 1 July 2010
Home < OpenIGTLink < ProtocolV2 < Type < PointContents
Summary
The POINT message type is designed to transfer information about fiducials, which are often used in surgical planning and navigation in the image-guided therapy.
Message Types
POINT
Data | Type | Description |
Name | char[64] | Name or description of the point |
Group name | char[32] | Can be "Labeled Point", "Landmark", "Fiducal", ... |
R,G,B,A | 8 bit unsigned | Color in RGBA |
X,Y,Z | 32 bit float | Coordinate of the point |
Diameter | 32 bit float | Diameter of the point, can be 0. |
Owner image | char[20] | Id of the owner image/sliceset. Points from different slicesets can be sent if slicesets are fused. |
GET_POINT
Data | Type | Description |
STT_POINT
N / A
STP_POINT
N / A
Implementations
XXX message type is implemented in the following source code.
- igtlXXXXMessage.h (link to the file in subversion repository, if available)
- igtlXXXXMessage.cxx (link to the file in subversion repository, if available)
Contributors
You may list names of contributors in this section.
Comments
People in the community may put comments here.