Captured tracking data can be exported in Comma Separated Values (CSV) format. This file format use comma delimiters to separate multiple values in each row, and it can be imported in a spreadsheet software or a programming script. Depending on which data export options are enabled, exported CSV files can contain marker data, rigid body data, and skeleton data. CSV export options are listed in the below chart.
Global: Sets 3D position data in respect to coordinate system at a global origin, which was defined with a ground plane during Calibration.
Local: Sets 3D position data of expected marker locations in respect to local segment axis on corresponding assets. These axes can be set to visible from Application Settings or display properties of assets in Project Pane.
Adds a column of Marker quality values after each rigid body marker data.
The quality stats display the reliability of associated marker data. Errors per marker lists average displacement between detected markers and expected marker locations within corresponding assets. Marker Quality values rate how well camera rays converged when respective marker was reconstructed. The value varies from 0 (unstable marker) to 1 (accurate marker).
When the header is disabled, these information will be excluded from the CSV files. Instead, the file will have frame IDs in the first column, time data on the second column, and the corresponding mocap data in the remaining columns. Header information will need to be acquired first in order to understand what data exists in each column.
TIP:Occlusion in the marker data
When there is any occlusion in a marker data, the CSV file will contain blank cells. This can interfere when running a script to process CSV data. It is recommended to optimize the capture setting to prevent occlusions. To omit unnecessary frame ranges with frequent marker occlusions, select frame range with best tracking results. Another solution to this is to use Fill Gaps to interpolate missing trajectories.