Difference between revisions of "OpenIGTLink/ProtocolV2/Type/Trajectory"

From NAMIC Wiki
Jump to: navigation, search
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
[[OpenIGTLink/ProtocolV2/Draft | << Version 2 Draft Page]]
+
[[OpenIGTLink/ProtocolV2/Index | << Version 2 Index Page]]
  
 
=Summary=
 
=Summary=
Line 5: Line 5:
  
 
=Message Types=
 
=Message Types=
==TRAJECTORY==
+
==TRAJ==
 
{| border="1" cellpadding="5" cellspacing="0" align="center"
 
{| border="1" cellpadding="5" cellspacing="0" align="center"
 
|-
 
|-
Line 69: Line 69:
  
 
N/A
 
N/A
 
  
 
=Implementations=
 
=Implementations=

Latest revision as of 04:43, 30 November 2011

Home < OpenIGTLink < ProtocolV2 < Type < Trajectory

<< Version 2 Index Page

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

TRAJ

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_TRAJ

N/A

Implementations

TRAJECTORY message type is implemented in the following source code.

Contributors

Alexander Schaal

Comments