For offline data analysis the system provides:
When you initiate data saving or when using our sample unity scene, the outputted data will be saved in you PC under the Documents folder but will differ depending on the application in use. For example:
On Pico Neo 3 Pro Eye (but may differ between apps):
This PC\Pico Neo 3 Pro Eye\Internal shared storage\Android\data\[Application Name]\cache
From each recording session you will find a
.dab and a
.json file. The
.dab file contains the sensor data and the
.json file containing the event markers created by the Unity SDK. Please refer to the SDK Data Point & Data Section for further information on the event markers.
In the following sections we will describe the general format of the sensor data (
.dab) saved when using the emteqPRO system, and how to convert it to a
.csvfile are explained further in section CSV specification.
As ‘sensor data file' we refer to the data collected as part of the
.dab file when using the Unity SDK and/or the SuperVision. The sensor data file (e.g. date_time_name.dab) is a binary formatted data file. The corresponding event file (
.json) will be named the same.
The .dab file contains
.dab file can be converted to comma separated files (csv) which can easily opened, read and consumed by external data processing software e.g. Python, MATLAB, and R.
Additional data points and affective insights can be added using our cloud based ML models. The process is explained in the section Obtaining affective insights.
If you wish to view your
.dab files in a CSV format you can simply upload via our SuperVision app. Follow these instructions on how to do perform the upload. By deselecting all insight options the ZIP file created will contain only the raw sensors information if that is all you need.
.eyedata file is generated in a separately, and also stored in a different location. It is generated by the tobii API and requires that the SRanipal service be running, as well as full integration into the Unity Application containing the Emteq SDK to provide object tracking within a scene. The file is named using the current date and time to make it easier to find, although the exact time may differ from the
.dab file created, since the API may begin recording at a different time.
In future this data may be combined into the
.dab for simplicity. There is currently no facility to upload via our Data Insights Upload facility. This data must be examined separately.
DETAILED CSV SPECIFICATION For version management, the official emteqPRO CSV Specification is available for reference. Please refer to this file for detailed row/column information by version.
.csv file generated contains all the data recorded from the time the data recording was triggered (see #Time/Seconds.referenceOffset) until the end of the recording. The .csv file will look similar to the one shown below
.csv file contains:
Information about the system and the frequency rates are exposed in the first section. In this example of a CSV above, line 32 contains the headers for each column corresponding to each sensor channel that is currently available in real-time. All comments are indicated by the symbol ‘#' at the start of the line. The system information contains the following: