Difference between revisions of "OpenIGTLink/ProtocolV2/Type/LabelMeta"
From NAMIC Wiki
(One intermediate revision by the same user not shown) | |||
Line 1: | Line 1: | ||
− | [[OpenIGTLink/ProtocolV2/ | + | [[OpenIGTLink/ProtocolV2/Index | << Version 2 Index Page]] |
=Summary= | =Summary= | ||
Line 62: | Line 62: | ||
=Implementations= | =Implementations= | ||
− | + | IMGMETA message type is implemented in the following source code. | |
− | * | + | *[http://svn.na-mic.org/NAMICSandBox/trunk/OpenIGTLink/Source/igtlLabelMetaMessage.h igtlLabelMetaMessage.h] |
− | * | + | *[http://svn.na-mic.org/NAMICSandBox/trunk/OpenIGTLink/Source/igtlLabelMetaMessage.cxx igtlLabelMetaMessage.cxx] |
=Contributors= | =Contributors= |
Latest revision as of 04:42, 30 November 2011
Home < OpenIGTLink < ProtocolV2 < Type < LabelMetaContents
Summary
To retreive voxel objects or a label map, GET_IMAGE / IMAGE can be used. But the client should be able to get a list of available structures. I suggest a GET_LBMETA message:
Message Types
LBMETA
Data | Type | Description |
Name/Description | char[64] | Name or description of the image |
Id | char[20] | Id to query the IMAGE |
Label | 8 bit unsigned int | Label of structure (0 if unused) |
-- | 8 bit unsigned int | Reserved. |
R,G,B,A | 8 bit unsigned | Color in RGBA (0 0 0 0 if no color is defined) |
RI, RJ, RK | 16 bit unsigned | Number of pixels in each direction (same as in IMAGE), bounding box of the structure(s) |
Owner image | char[20] | Id of the owner image/sliceset. Voxel objects from different slicesets can be sent if slicesets are fused. Can be empty if n/a. |
GET_LBMETA
Data | Type | Description |
STT_LBMETA
N/A
STP_LBMETA
N/A
Implementations
IMGMETA message type is implemented in the following source code.
Contributors
Alexander Schaal