This article will help you understand how your downloaded Movesense data is organized with Labfront.
How the Folders are Organized
Labfront creates a single ZIP file of all of your participants' data, labeled with your unique Project ID.
As you can see below, each participant has their own folder labeled with their Participant Insignia (name inputted by the researcher) and Participant ID (unique identifier).
In the participant folder are CSV files organized into subfolders by data source and/or tasks. Your Movesense physiological data CSV files will be located in the movesense-stream folder.
Every Movesense task will have its own folder labeled with the task name, within which are subfolders for each instance of the Movesense task (labeled with the Unix timestamp of the task's start) and the data types collected (IMU, RR-Interval, and/or ECG).
For example, here is an Exercise Recovery task that was completed twice. You can see the timestamped subfolders for each instance of the task and subfolders for each data type collected (movesense-stream-imu and movesense-stream-rr):
Movesense tasks are organized this way because each task can record lots of data, and can use different sensors at different resolutions, but they should all be contained together for easier analysis.
You will also see a movesense-stream-stopwatch-event file. This file does not contain physiological data but displays when participants stopped and started the Movesense task and keeps a record of each instance.
How Movesense CSV Files are Organized
The CSV files in every folder are numbered beginning with 000000. If a file exceeds the maximum amount of rows permitted, a new CSV file will be created and numbered sequentially (Ex. 000001, 000002, etc.).
Your project, participant, and task details are located in the Header of every CSV file. The Header length (in this example it's 5) means that the subsequent 5 rows are part of the Header and do not contain participant data.
For a list of variables included in the Header and their descriptions, you can view this table:
Within each data type's CSV file, each row represents one data recording.
Sample IMU data:
Sample ECG data:
Sample RR-Interval data:
View our documentation on Movesense data types and descriptions→
Data Documentation Resource
Access our data documentation PDF for a data dictionary of metrics you can collect with Labfront and their meanings.
➕ Additional Information About Your Data
For a better understanding of your data, we suggest reading the following articles:
Why does Labfront use Unix time?
The Unix timestamp is the number of seconds between a particular date and the Unix Epoch (Jan 1, 1970). Since this point in time technically does not change no matter where you are located on the globe, it's very useful for accurately comparing and manipulating dates and times across different platforms and time zones.
Do you offer any services to help analyze the data?