Vicon:Data format documentation

From Collective Computational Unit
Revision as of 13:57, 19 June 2019 by Bastian.goldluecke (talk | contribs) (Raw data)
Jump to navigation Jump to search

Raw data

TODO: quick description of what exactly the Vicon system records.

TODO: quick description of what the input/output of the different Vicon software modules is. For example, do you need to run any software to obtain the unlabeled trajectories, or is that part of the raw output of the system?

TODO: 3D coordinates of backpack points for each backpack (in Backpack coordinates). Is this really an output of the system, i.e. does it find rigid patterns itself? It sounds like it's more of a configuration one has to supply in order to extract backpack positions from unlabeled trajectories.

A Python script can extract information (which?), however data packet can be lost if too many objects are saved. Need optimization.

Resources:

Unlabeled trajectories

  • Tracker unlabeled trajectory (.csv) : 3D position of each marker (backpack or no backpack) (Vicon coordinate system - X,Y,Z). Will have similar points in single column as trajectories if tracked well, when lost position is saved in new columns.
TODO: maybe a few lines of the CSV file as examples to illustrate the above.
  • Unlabeled points (not on backpack or pattern) can be extracted in real time. (in VICON space)


An example CSV file was placed online by Mate here:

Google drive link

Nexus/Tracker output

  1. Tracker output (.csv): 6DOF of each pattern design/backpack (Quaternions, Tx,Ty,Tz in Vicon coordinate system)
  2. Nexus output : 3D position of each marker on backpack (.csv) (Tx,Ty,Tz) (in Vicon coordinate system)

The second can obviously be generated from the first together with the backpack patterns in their local coordinate systems.

However, Nexus and Tracker have different outputs. (TODO: what does this mean?)