integration:vicon
Unterschiede
Hier werden die Unterschiede zwischen zwei Versionen angezeigt.
Beide Seiten der vorigen RevisionVorhergehende ÜberarbeitungNächste Überarbeitung | Vorhergehende Überarbeitung | ||
integration:vicon [2021/09/21 16:26] – oliver | integration:vicon [2022/01/27 19:54] (aktuell) – oliver | ||
---|---|---|---|
Zeile 49: | Zeile 49: | ||
^ bufferSize | The size of the receiving data buffer. Default value is 1 | Yes | | ^ bufferSize | The size of the receiving data buffer. Default value is 1 | Yes | | ||
^ isMarkerDataEnabled | Should labeled marker data be transmitted and avaiable to be saved. | Yes | | ^ isMarkerDataEnabled | Should labeled marker data be transmitted and avaiable to be saved. | Yes | | ||
+ | ^ isMarkerRayDataEnabled | Should marker ray data be transmitted and avaiable to be saved. | Yes | | ||
+ | ^ isDeviceDataEnabled | Should device data be transmitted and avaiable to be saved. | Yes | | ||
^ isUnlabeledMarkerDataEnabled | Should unabled marker data be transmitted and avaiable to be saved. | Yes | | ^ isUnlabeledMarkerDataEnabled | Should unabled marker data be transmitted and avaiable to be saved. | Yes | | ||
^ isSegmentDataEnabled | Should segment data be transmitted and avaiable to be saved. | Yes | | ^ isSegmentDataEnabled | Should segment data be transmitted and avaiable to be saved. | Yes | | ||
+ | ^ isLightweightSegmentDataEnabled | Should segment data be transmitted and avaiable to be saved. | Yes | | ||
^ isVideoDataEnabled | Should video data be transmitted and avaiable to be saved. | Yes | | ^ isVideoDataEnabled | Should video data be transmitted and avaiable to be saved. | Yes | | ||
^ isCentroidDataEnabled | Should centroid data be transmitted and available to be saved. | Yes | | ^ isCentroidDataEnabled | Should centroid data be transmitted and available to be saved. | Yes | | ||
Zeile 57: | Zeile 60: | ||
Keep in mind: The first frame got by the ViconDataStream is always 0. This seems to be a bug in the Vicon DataStream API. | Keep in mind: The first frame got by the ViconDataStream is always 0. This seems to be a bug in the Vicon DataStream API. | ||
+ | |||
+ | The channel names are fix for the markers and segments but are configurable in principle for devices. TransducerUnitGroups with the names listed in the following table have a specific meaning. All other names are interpreted as subject names corresponding to the names configured in Vicon Tracker/ | ||
+ | |||
+ | ^ tranducer unit group name ^ Description ^ | ||
+ | ^ markers | This group contains units corresponding to markers | | ||
+ | ^ devices | This group contains units corresponding to devices | | ||
+ | |||
+ | Marker unit can have channels with the names shown in the following table: | ||
+ | |||
+ | ^ channel name ^ Description ^ | ||
+ | ^ v0 | x coordinate of the position of the marker | | ||
+ | ^ v1 | y coordinate of the position of the marker | | ||
+ | ^ v2 | z coordinate of the position of the marker | | ||
+ | ^ T | timestamp corresponding to the marker. | | ||
+ | ^ q | quality of the tracking of the marker | | ||
+ | |||
+ | Segment units can have channels with the names shown in the following table: | ||
+ | |||
+ | ^ channel name ^ Description ^ | ||
+ | ^ v0 | x coordinate of the position of the marker | | ||
+ | ^ v1 | y coordinate of the position of the marker | | ||
+ | ^ v2 | z coordinate of the position of the marker | | ||
+ | ^ q0 || | ||
+ | ^ q1 || | ||
+ | ^ q2 || | ||
+ | ^ q3 || | ||
+ | ^ T | timestamp corresponding to the marker. | | ||
+ | ^ q | quality of the tracking of the marker | | ||
+ | |||
+ |
integration/vicon.1632234363.txt.gz · Zuletzt geändert: 2021/09/21 16:26 von oliver