integration:vicon
Unterschiede
Hier werden die Unterschiede zwischen zwei Versionen angezeigt.
Beide Seiten der vorigen RevisionVorhergehende ÜberarbeitungNächste Überarbeitung | Vorhergehende Überarbeitung | ||
integration:vicon [2020/11/18 17:15] – oliver | integration:vicon [2022/01/27 19:54] (aktuell) – oliver | ||
---|---|---|---|
Zeile 1: | Zeile 1: | ||
=====Vicon measurement system integration===== | =====Vicon measurement system integration===== | ||
The Vicon-integration is based on [[https:// | The Vicon-integration is based on [[https:// | ||
+ | |||
+ | The value of the attribute " | ||
**Example configuration fragment:** | **Example configuration fragment:** | ||
Zeile 12: | Zeile 14: | ||
< | < | ||
< | < | ||
- | < | + | <!--Property name=" |
- | < | + | < |
< | < | ||
<Channel name=" | <Channel name=" | ||
Zeile 26: | Zeile 28: | ||
</ | </ | ||
... | ... | ||
- | < | + | < |
| | ||
< | < | ||
Zeile 44: | Zeile 46: | ||
^ Property name ^ Description ^ Optional | | ^ Property name ^ Description ^ Optional | | ||
- | ^ dnsidentifiablename| A name possibly resolveable by the DNS | No | | + | ^ dnsidentifiablename | A name possibly resolveable by the DNS | No | |
- | ^ timeout| timeout | + | ^ bufferSize |
+ | ^ 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 | | ||
+ | ^ 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 | | ||
+ | ^ isCentroidDataEnabled | Should centroid data be transmitted and available to be saved. | Yes | | ||
+ | ^ isGreyscaleDataEnabled | Should greyscaledata be transmitted and available to be saved. | Yes | | ||
+ | ^ streamingMode | ClientPull or ClientPullPreFetch or ServerPush | Yes | | ||
+ | |||
+ | 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.txt · Zuletzt geändert: 2022/01/27 19:54 von oliver