This wiki is intended for older versions of Motive. For the latest documentation, please refer to
docs.optitrack.com

Difference between revisions of "Data Export: CSV"

Line 17: Line 17:
 
|-
 
|-
 
|style="padding: 10px;"|Rigid Bodies
 
|style="padding: 10px;"|Rigid Bodies
|style="padding: 10px;"|When this option is set to true, exported CSV file will contain 6 DoF data for each rigid body from the Take. 6 DoF data contain orientations (pitch,roll, and yaw in the chosen '''rotation type''' as well as 3D positions (x,y,z) of the rigid body center.
+
|style="padding: 10px;"|When this option is set to true, exported CSV file will contain 6 Degree of Freedom (6 DoF) data for each rigid body from the Take. 6 DoF data contain orientations (pitch,roll, and yaw in the chosen '''rotation type''' as well as 3D positions (x,y,z) of the rigid body center.
 
|-
 
|-
 
|style="padding: 10px;"|RigidBodyMarkers
 
|style="padding: 10px;"|RigidBodyMarkers
|style="padding: 10px;"|Enabling this option includes 3D position data for each [[Data Recording#Expected Marker Positions: Rigid Body Markers and Bone Markers|expected marker locations]] within rigid body assets.
+
|style="padding: 10px;"|Enabling this option includes 3D position data for each [[Data Recording#Expected Marker Positions: Rigid Body Markers and Bone Markers|expected marker locations]] (not actual marker location) within rigid body assets.
 
|-
 
|-
 
|style="padding: 10px;"|Bones
 
|style="padding: 10px;"|Bones
Line 26: Line 26:
 
|-
 
|-
 
|style="padding: 10px;"|BoneMarkers
 
|style="padding: 10px;"|BoneMarkers
|style="padding: 10px;"|Enabling this option will include 3D position data for each [[Data Recording#Expected Marker Positions: Rigid Body Markers and Bone Markers|expected marker locations]] within skeleton assets.
+
|style="padding: 10px;"|Enabling this option will include 3D position data for each [[Data Recording#Expected Marker Positions: Rigid Body Markers and Bone Markers|expected marker locations]] (not actual marker location) within skeleton assets.
 
|-
 
|-
 
|style="padding: 10px;"|Rotation Type
 
|style="padding: 10px;"|Rotation Type
Line 86: Line 86:
 
{{Tip|'''TIP:Occlusion in the marker data'''
 
{{Tip|'''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 [[Data Editing#Fill Gaps|Fill Gaps]] to interpolate missing trajectories.}}
+
When there is an 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 [[Data Editing#Fill Gaps|Fill Gaps]] to interpolate missing trajectories.}}

Revision as of 23:18, 23 November 2015

Back to the Main PageBack to Motive DocumentationBack to Data Export

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.


CSV Export Options
CSV Options Description
Unit Sets units for positional data in exported CSV files
Markers Enabling this option includes X/Y/Z reconstructed 3D positions for each marker in exported CSV files.
Rigid Bodies When this option is set to true, exported CSV file will contain 6 Degree of Freedom (6 DoF) data for each rigid body from the Take. 6 DoF data contain orientations (pitch,roll, and yaw in the chosen rotation type as well as 3D positions (x,y,z) of the rigid body center.
RigidBodyMarkers Enabling this option includes 3D position data for each expected marker locations (not actual marker location) within rigid body assets.
Bones When this option is set to true, exported CSV files will include 6 DoF data for each bone segment of skeletons in exported Takes. 6 DoF data contain orientations (pitch, roll, and yaw) in the chosen rotation type, and also 3D positions (x,y,z) for the center of the bone.
BoneMarkers Enabling this option will include 3D position data for each expected marker locations (not actual marker location) within skeleton assets.
Rotation Type Rotation type determines whether Quaternion or Euler Angles is used for orientation convention in exported CSV files. For Euler rotation, all different orders of elemental rotation is available
Coordinate Space This option decides whether exported data will be based on global or local coordinate system.

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.

Quality Stats Adds a column of Error per marker values for each rigid body position data.

Adds a column of Marker quality values after each rigid body marker data.

Include Header information Includes detailed information about capture data as a header in exported CSV files. Types of information included in the header section is listed in the following section.


Errors in the data, Quality Stats

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).


CSV Header

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.


CSV Headers
Row Description
1st row General information about the Take and export settings. Included information are: format version of the CSV export, name of the TAK file, the captured frame rate, the export frame rate, capture start time, number of total frames, rotation type, length units, and coordinate space type.
2nd row Empty
3rd row Displays which data type is listed in each corresponding column. Data types include raw marker, rigid body, rigid body marker, bone, bone marker, or unlabeled marker. Read more about Marker Types.
4th row Includes marker or asset labels for each corresponding data set.
5th row Displays marker ID.
6th and 7th row Includes header label on which data is included in the column: position and orientation on X/Y/Z.


DataExport CSV.png


TIP:Occlusion in the marker data

When there is an 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.