Difference between revisions of "OpenIGTLink/ProtocolV2/Type/PolyData"
From NAMIC Wiki
| Line 43: | Line 43: | ||
| align="left" | NPOLYGONS | | align="left" | NPOLYGONS | ||
| align="left" | uint32 | | align="left" | uint32 | ||
| − | | align="left" | Number of | + | | align="left" | Number of polygons |
|- | |- | ||
| align="left" | SIZE_POLYGONS | | align="left" | SIZE_POLYGONS | ||
| align="left" | uint32 | | align="left" | uint32 | ||
| − | | align="left" | Number of | + | | align="left" | Number of polygons |
|- | |- | ||
| align="left" | NTRIANGLE_STRIPS | | align="left" | NTRIANGLE_STRIPS | ||
| align="left" | uint32 | | align="left" | uint32 | ||
| − | | align="left" | Number of | + | | align="left" | Number of triangle strips |
|- | |- | ||
| align="left" | SIZE_TRIANGLE_STRIPS | | align="left" | SIZE_TRIANGLE_STRIPS | ||
| align="left" | uint32 | | align="left" | uint32 | ||
| − | | align="left" | Number of | + | | align="left" | Number of triangle strips |
| + | |- | ||
| + | | align="left" | NATTRIBUTES | ||
| + | | align="left" | uint32 | ||
| + | | align="left" | Number of dataset attributes | ||
| + | |- | ||
| + | | align="left" | TYPE_ATTRIBUTE1 | ||
| + | | align="left" | uint16 | ||
| + | | align="left" | Type of dataset attribute 1 (including number of components for scalar type) | ||
| + | |- | ||
| + | | align="left" | NAMESIZE_ATTRIBUTE1 | ||
| + | | align="left" | uint16 | ||
| + | | align="left" | Length of name for attribute 1 | ||
| + | |- | ||
| + | | align="left" | SIZE_ATTRIBUTE1 | ||
| + | | align="left" | uint32 | ||
| + | | align="left" | Number of data for attribute1 | ||
| + | |- | ||
| + | | align="left" | TYPE_ATTRIBUTE2 | ||
| + | | align="left" | uint16 | ||
| + | | align="left" | Type of dataset attribute 1 (including number of components for scalar type) | ||
| + | |- | ||
| + | | align="left" | NAMESIZE_ATTRIBUTE2 | ||
| + | | align="left" | uint16 | ||
| + | | align="left" | Length of name for attribute 2 | ||
| + | |- | ||
| + | | align="left" | SIZE_ATTRIBUTE2 | ||
| + | | align="left" | uint32 | ||
| + | | align="left" | Number of data for attribute2 | ||
| + | |- | ||
| + | | align="left" | ... | ||
| + | | align="left" | ... | ||
| + | | align="left" | ... | ||
| + | |- | ||
| + | | align="left" | TYPE_ATTRIBUTE(NATTRIBUTES) | ||
| + | | align="left" | uint16 | ||
| + | | align="left" | Type of dataset attribute 1 (including number of components for scalar type) | ||
| + | |- | ||
| + | | align="left" | NAMESIZE_ATTRIBUTE(NATTRIBUTES) | ||
| + | | align="left" | uint16 | ||
| + | | align="left" | Length of name for attribute 2 | ||
| + | |- | ||
| + | | align="left" | SIZE_ATTRIBUTE(NATTRIBUTES) | ||
| + | | align="left" | uint32 | ||
| + | | align="left" | Number of data for attribute2 | ||
|- | |- | ||
| align="left" | POINTS | | align="left" | POINTS | ||
Revision as of 21:17, 28 July 2011
Home < OpenIGTLink < ProtocolV2 < Type < PolyDataContents
Summary
POLYDATA is used to transfer 3D polygonal data. The message format is designed based on the POLY DATA format defined in VTK file format and equivalent to VTK's vtkPolyData class.
Message Types
POLYDATA
| Data | Type | Description |
| NPOINTS | uint32 | Number of points |
| PTYPE | uint8 | Data type (see image) |
| (Reserved) | uint8 | -- |
| NVERTICES | uint32 | Number of vertices |
| SIZE_VERTICES | uint32 | Number of vertices |
| NLINES | uint32 | Number of lines |
| SIZE_LINES | uint32 | Number of lines |
| NPOLYGONS | uint32 | Number of polygons |
| SIZE_POLYGONS | uint32 | Number of polygons |
| NTRIANGLE_STRIPS | uint32 | Number of triangle strips |
| SIZE_TRIANGLE_STRIPS | uint32 | Number of triangle strips |
| NATTRIBUTES | uint32 | Number of dataset attributes |
| TYPE_ATTRIBUTE1 | uint16 | Type of dataset attribute 1 (including number of components for scalar type) |
| NAMESIZE_ATTRIBUTE1 | uint16 | Length of name for attribute 1 |
| SIZE_ATTRIBUTE1 | uint32 | Number of data for attribute1 |
| TYPE_ATTRIBUTE2 | uint16 | Type of dataset attribute 1 (including number of components for scalar type) |
| NAMESIZE_ATTRIBUTE2 | uint16 | Length of name for attribute 2 |
| SIZE_ATTRIBUTE2 | uint32 | Number of data for attribute2 |
| ... | ... | ... |
| TYPE_ATTRIBUTE(NATTRIBUTES) | uint16 | Type of dataset attribute 1 (including number of components for scalar type) |
| NAMESIZE_ATTRIBUTE(NATTRIBUTES) | uint16 | Length of name for attribute 2 |
| SIZE_ATTRIBUTE(NATTRIBUTES) | uint32 | Number of data for attribute2 |
| POINTS | PTYPE * NPOINTS * 3 | Coordinates of points (P0x, P0y, P0z, P1x, P1y, P1z, ... P(n-1)x, P(n-1)y, P(n-1)z |
| VERTICES | uint32 * ((NPOINTS_0+1) + (NPOINTS_1+1) + (NPOINTS_(N-1)+1)) | array of vertices ((NPOINTS_0, index_0_0, index_0_1, ....), (NPOINTS_1, index_1_0, index_1_1, ....), ..., (NPOINTS_(N-1), index_(N-1)_0, index_(N-1)_1, ....)) |
| LINES | uint32 * ((NPOINTS_0+1) + (NPOINTS_1+1) + (NPOINTS_(N-1)+1)) | array of vertices ((NPOINTS_0, index_0_0, index_0_1, ....), (NPOINTS_1, index_1_0, index_1_1, ....), ..., (NPOINTS_(N-1), index_(N-1)_0, index_(N-1)_1, ....)) |
| POLYGONS | uint32 * ((NPOINTS_0+1) + (NPOINTS_1+1) + (NPOINTS_(N-1)+1)) | array of vertices ((NPOINTS_0, index_0_0, index_0_1, ....), (NPOINTS_1, index_1_0, index_1_1, ....), ..., (NPOINTS_(N-1), index_(N-1)_0, index_(N-1)_1, ....)) |
| TRIANGLE_STRIPS | uint32 * ((NPOINTS_0+1) + (NPOINTS_1+1) + (NPOINTS_(N-1)+1)) | array of vertices ((NPOINTS_0, index_0_0, index_0_1, ....), (NPOINTS_1, index_1_0, index_1_1, ....), ..., (NPOINTS_(N-1), index_(N-1)_0, index_(N-1)_1, ....)) |
2/17 change the order of the field to make implementation easier
GET_POLYDATA
| Data | Type | Description |
STT_POLYDATA
| Data | Type | Description |
| Data | Type | Description |
| RESOL | uint64 | Minimum interval between message (ns). Same format as TimeStamp |
STP_POLYDATA
| Data | Type | Description |
RTS_POLYDATA
| Data | Type | Description |
| Status | 8 bit unsigned | 0: Success 1: Error |
Implementations
The NDARRAY message type is implemented in the following source code.
Contributors
Junichi Tokuda
