Difference between revisions of "OpenIGTLink/ProtocolV2/Type/Trajectory"
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 TRAJECTORY message type support to transfer information about 3D trajectory, which is often used in surgical planning and guidance in image-guided therapy. |
=Message Types= | =Message Types= | ||
− | == | + | ==TRAJECTORY== |
− | |||
{| border="1" cellpadding="5" cellspacing="0" align="center" | {| border="1" cellpadding="5" cellspacing="0" align="center" | ||
|- | |- | ||
Line 13: | Line 12: | ||
| 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 trajectory. |
+ | |- | ||
+ | | align="left" | Group name | ||
+ | | align="left" | char[32] | ||
+ | | align="left" | Can be "Trajectory", ... | ||
|- | |- | ||
− | | align="left" | | + | | align="left" | Type |
− | | align="left" | | + | | align="left" | 8 bit unsigned |
− | | align="left" | | + | | align="left" | 1: trajectory with only entry point, 2: trajectory with only target point, 3: trajectory with entry and target point |
|- | |- | ||
− | | align="left" | | + | | align="left" | -- |
− | | align="left" | | + | | align="left" | 8 bit unsigned |
− | | align="left" | | + | | align="left" | Reserved |
|- | |- | ||
− | | | + | | align="left" | R,G,B,A |
− | + | | align="left" | 8 bit unsigned | |
− | + | | align="left" | Color in RGBA | |
− | |||
− | |||
|- | |- | ||
− | | align="left | + | | align="left" | X1,Y1,Z1 |
− | | align="left | + | | align="left" | 32 bit float |
− | | align="left | + | | align="left" | Entry point of the trajectory |
|- | |- | ||
− | | align="left" | | + | | align="left" | X2,Y2,Z2 |
− | | align="left" | | + | | align="left" | 32 bit float |
− | | align="left" | | + | | align="left" | Target point of a trajectory |
|- | |- | ||
− | | align="left" | | + | | align="left" | Diameter |
− | | align="left" | | + | | align="left" | 32 bit float |
− | | align="left" | | + | | align="left" | Diameter of trajectory, 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. Trajectories from different slicesets can be sent if slicesets are fused. |
|- | |- | ||
|} | |} | ||
− | == | + | ==GET_TRAJ== |
{| border="1" cellpadding="5" cellspacing="0" align="center" | {| border="1" cellpadding="5" cellspacing="0" align="center" | ||
Line 57: | Line 58: | ||
| 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_TRAJ== | ||
+ | |||
+ | N/A | ||
==STP_XXXX== | ==STP_XXXX== | ||
− | + | N/A | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
=Implementations= | =Implementations= |
Revision as of 03:01, 1 July 2010
Home < OpenIGTLink < ProtocolV2 < Type < TrajectoryContents
Summary
The TRAJECTORY message type support to transfer information about 3D trajectory, which is often used in surgical planning and guidance in image-guided therapy.
Message Types
TRAJECTORY
Data | Type | Description |
Name | char[64] | Name or description of the trajectory. |
Group name | char[32] | Can be "Trajectory", ... |
Type | 8 bit unsigned | 1: trajectory with only entry point, 2: trajectory with only target point, 3: trajectory with entry and target point |
-- | 8 bit unsigned | Reserved |
R,G,B,A | 8 bit unsigned | Color in RGBA |
X1,Y1,Z1 | 32 bit float | Entry point of the trajectory |
X2,Y2,Z2 | 32 bit float | Target point of a trajectory |
Diameter | 32 bit float | Diameter of trajectory, can be 0 |
Owner image | char[20] | Id of the owner image/sliceset. Trajectories from different slicesets can be sent if slicesets are fused. |
GET_TRAJ
Data | Type | Description |
STT_TRAJ
N/A
STP_XXXX
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.