Benutzer-Werkzeuge

Webseiten-Werkzeuge


integration:vicon

Unterschiede

Hier werden die Unterschiede zwischen zwei Versionen angezeigt.

Link zu dieser Vergleichsansicht

Beide Seiten der vorigen RevisionVorhergehende Überarbeitung
Nächste Überarbeitung
Vorhergehende Überarbeitung
Letzte ÜberarbeitungBeide Seiten der Revision
integration:vicon [2021/01/25 17:16] oliverintegration:vicon [2022/01/27 19:50] oliver
Zeile 2: Zeile 2:
 The Vicon-integration is based on [[https://github.com/MobMonRob/JViconDataStream2|JDataAquisition]], a java library wrapper of Vicons [[https://www.vicon.com/software/datastream-sdk/|DataStream SDK]]. Connections to one or more running Vicon systems are possible.  The Vicon-integration is based on [[https://github.com/MobMonRob/JViconDataStream2|JDataAquisition]], a java library wrapper of Vicons [[https://www.vicon.com/software/datastream-sdk/|DataStream SDK]]. Connections to one or more running Vicon systems are possible. 
  
-The value of the attribute "system" from the element <MeasurementSystem> hast to be set to "Vicon".+The value of the attribute "system" from the element <MeasurementSystem> has to be set to "Vicon".
  
 **Example configuration fragment:** **Example configuration fragment:**
Zeile 47: Zeile 47:
 ^ 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 |
-^ bufferSize | The size of the receiving data buffer. Default value is 1 | No +^ 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. | No +^ isMarkerDataEnabled | Should labeled marker data be transmitted and avaiable to be saved. | Yes | 
-^ isUnlabeledMarkerDataEnabled | Should unabled marker data be transmitted and avaiable to be saved. | No +^ isMarkerRayDataEnabled | Should marker ray data be transmitted and avaiable to be saved. | Yes | 
-^ isSegmentDataEnabled | Should segment data be transmitted and avaiable to be saved. | No +^ isDeviceDataEnabled | Should device data be transmitted and avaiable to be saved. | Yes 
-^ isVideoDataEnabled | Should video data be transmitted and avaiable to be saved. | No |+^ 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/Nexus.  
 + 
 +^ tranducer unit group name ^ Description ^ 
 +^ markers | This group contains units corresponding to markers |  
 +^ devices | This group contains units corresponding to devices |  
 + 
 + 
integration/vicon.txt · Zuletzt geändert: 2022/01/27 19:54 von oliver

Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki