Data Export: CSV
CSV Export
Captured tracking data can be exported in Comma Separated Values (CSV) format. This file format uses comma delimiters to separate multiple values in each row, which can be imported by spreadsheet software or a programming script. Depending on which data export options are enabled, exported CSV files can contain marker data, and data for Rigid Bodies, Trained Markersets, and/or Skeletons. Data for force plate, NI-DAQs, and other devices will export to separate files if these devices are included in the Take.
CSV export options are listed in the following charts:
General Export Options
Frame Rate
Number of samples included per second of exported data.
Start Frame
Start frame of the exported data. Set to one of the following:
The recorded first frame of the exported Take (the default option).
Custom to enter a specific frame number.
End Frame
End frame of the exported data. Set to one of the following:
The recorded end frame of the exported Take (the default option).
Custom to enter a specific frame number.
Scale
Apply scaling to the exported tracking data.
Units
Set the measurement units to use for exported data.
Axis Convention
Sets the axis convention on exported data. This can be set to a custom convention or select preset conventions for Entertainment or Measurement.
X Axis Y Axis Z Axis
Allows customization of the axis convention in the exported file by determining which positional data to be included in the corresponding data set.
CSV Export Options
Header information
Markers
X/Y/Z reconstructed 3D positions for each marker in exported CSV files.
Unlabeled Markers
Includes tracking data of all of the unlabeled makers to the exported CSV file along with other labeled markers. To view only the labeled marker data, turn off this export setting.
Rigid Body Bones
The exported CSV file will contain 6 Degrees of Freedom (6 DoF) data for each rigid body from the Take. This includes orientations (pitch, roll, and yaw) in the chosen rotation type as well as 3D positions (x,y,z) of the rigid body center.
Rigid Body Constraints
3D position data for the location of each Marker Constraint of rigid body assets. This is distinct from the actual marker location. Compared to the positions of the raw marker positions included within the Markers columns, the Rigid Body Constraints show the solved positions of the markers as affected by the rigid body tracking but not affected by occlusions.
Skeleton and Markerset Bones
The exported CSV files will include 6 DoF data for each bone segment of skeletons and trained markersets 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. All skeleton and markerset assets must be solved to export this data.
Bone Constraints
3D position data for the location of each Marker Constraint of bone segments in skeleton and trained markerset assets. Compared to the real marker positions included within the Markers columns, the Bone Markers show the solved positions of the markers as affected by the skeleton tracking but not affected by occlusions.
Exclude Fingers
Exported skeletons will not include the fingers, if they are tracked in the Take file.
Asset Hip Name
When selected, the hip bone data is labeled as Asset_Name:Asset_Name (e.g., Skeleton:Skeleton). When unselected, the exported data will use the classic Motive naming convention of Asset_Name:Hip (e.g., Skeleton:Hip).
Rotation Type
Rotation type determines whether Quaternion or Euler Angles are used for orientation convention in exported CSV files. For Euler rotation, right-handed coordinate system is used and all different orders (XYZ, XZY, YXZ, YZX, ZXY, ZYX) of elemental rotation are available. More specifically, the XYZ order indicates pitch is degree about the X axis, yaw is degree about the Y axis, and roll is degree about the Z axis.
This option determines whether exported data will be based on world (global) or local coordinate systems.
Device Data
Exports separate CSV files for recorded device data. This includes force plate data and analog data from NI-DAQ devices. A CSV file is exported for each device included in the Take.
Coordinate Systems
Coordinates for exported data are either global to the volume or local to the asset.
Global or World Coordinates
Local Coordinates
Defines the bone position and orientation in respect to the coordinate system of the parent bone.
Physical Markers vs Marker Constraints During Occlusion
In the CSV file, Rigid Body markers have a physical marker column and a Marker Constraints column.
When a marker is occluded in Motive, the Marker Constraints will display the solved position for where the marker should be in the CSV file. The actual physical marker will display a blank cell or null value since Motive cannot account for its actual location due to its occlusion.
CSV Header
When the header is disabled, this information is 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.
CSV Headers
1st row
General information about the Take and export settings: Format version of the CSV export, name of the TAK file, the captured frame rate, the export frame rate, capture start time, capture start frame, number of total frames, total exported frames, rotation type, length units, and coordinate space type.
2nd row
Empty
3rd row
4th row
Includes marker or asset labels for each corresponding data set.
5th row
Displays marker or asset ID.
6th and 7th rows
Shows which data is included in the column: rotation or position and orientation on X/Y/Z.
Force Plate Data / Analog Data
Force Plate Data: Each of the force plate CSV files will contain basic properties such as platform dimensions and mechanical-to-electrical center offset values. The mocap frame number, force plate sample number, forces (Fx/Fy/Fz), moments (Mx, My, Mz), and location of the center of pressure (Cx, Cy, Cz) will be listed below the header.
Analog Data: Each of the analog data CSV files contains analog voltages from each configured channel.
Last updated
Was this helpful?