subject stringclasses 1
value | session stringlengths 3 3 | setting stringclasses 2
values | surface stringclasses 3
values | hr_mean_bpm float64 139 170 ⌀ | hr_max_bpm float64 151 199 ⌀ | hr_source stringclasses 2
values | cadence_mean_spm float64 143 158 ⌀ | cadence_source stringclasses 1
value |
|---|---|---|---|---|---|---|---|---|
S01 | R01 | outdoor | pavement | 156 | 170 | fit3_watch | 144 | phone_steps |
S01 | R02 | outdoor | pavement | 159 | 178 | polar_h10 | 154 | phone_steps |
S01 | R03 | outdoor | pavement | 146 | 161 | polar_h10 | 147 | phone_steps |
S01 | R04 | outdoor | pavement | 148 | 160 | fit3_watch | 149 | phone_steps |
S01 | R05 | indoor | track | 158 | 183 | polar_h10 | 148 | phone_steps |
S01 | R06 | outdoor | pavement | 164 | 182 | fit3_watch | 154 | phone_steps |
S01 | R07 | outdoor | pavement | 144 | 161 | fit3_watch | 152 | phone_steps |
S01 | R08 | outdoor | pavement | 151 | 170 | fit3_watch | 151 | phone_steps |
S01 | R09 | outdoor | pavement | 160 | 178 | fit3_watch | null | null |
S01 | R10 | outdoor | pavement | 157 | 171 | fit3_watch | null | null |
S01 | R11 | indoor | track | 145 | 176 | fit3_watch | null | null |
S01 | R12 | outdoor | pavement | 170 | 199 | fit3_watch | null | null |
S01 | R13 | outdoor | pavement | 142 | 158 | fit3_watch | 149 | phone_steps |
S01 | R14 | indoor | track | null | null | null | 143 | phone_steps |
S01 | R15 | indoor | track | null | null | null | 148 | phone_steps |
S01 | R16 | outdoor | pavement | null | null | null | 157 | phone_steps |
S01 | R17 | outdoor | pavement | 146 | 155 | fit3_watch | null | null |
S01 | R18 | indoor | track | 139 | 151 | polar_h10 | 149 | phone_steps |
S01 | R19 | indoor | track | 152 | 180 | polar_h10 | 150 | phone_steps |
S01 | R20 | outdoor | grass;dirt;pavement | 161 | 174 | fit3_watch | 158 | phone_steps |
S01 | R21 | outdoor | pavement | null | null | null | 158 | phone_steps |
S01 | R22 | outdoor | grass;dirt;pavement | null | null | null | 152 | phone_steps |
S01 | R23 | outdoor | pavement | null | null | null | 158 | phone_steps |
S01 | R24 | indoor | track | null | null | null | 146 | phone_steps |
S01 | R25 | outdoor | pavement | null | null | null | 158 | phone_steps |
LEVEL Running Dataset
Open, raw running recordings from body-worn LEVEL motion sensors (feet, lower back, wrist, arm), time-synchronized with a Polar H10 chest strap (heart rate, RR intervals, ECG), phone GPS, barometer and step counter, and additional ground truth where available. Collected with the LEVEL Collector platform, which runs on Android phones and Windows PCs, across deliberately varied sensor setups, and tracked run over run for open research on running performance, fatigue and injury prevention.
In 2025, my doctor gave me "the talk." You know the one. The one where I need to exercise more and eat better. So I picked up running, and somewhere along the way I thought: I'm a biomechanics engineer, and I work for a company that makes IMU motion sensors. Why not take some measurements?
Two purposes
1. LEVEL Collector, working anywhere. An open record of the collection platform itself: different sensors, placements, settings and devices, in and out of the research lab. LEVEL Inez is a small wearable 6-axis motion sensor (accelerometer ±16 g, gyroscope) that clips or straps onto the body -- here both feet, the lower back and a wrist or arm -- and streams for about 36 hours (a day and a half) at 100 Hz on a charge. LEVEL Collector is the research app that records several of them at once, over the phone's Bluetooth or the LEVEL Hub USB receiver, with the sensor clocks kept in step, alongside the phone's GPS, barometer and step counter and add-ons such as a Polar H10 chest strap, all on one clock, as plain documented CSV files (the format spec).
2. Running research. A longitudinal, within-participant record of real running: pace, heart rate, cadence and foot mechanics across runs, conditions and fatigue. Almost all running-injury research compares runners with each other, cross-sectionally or in prospective cohorts with a single baseline measurement, so following a runner's own mechanics over time is still rare; and the public running-IMU datasets are nearly all lab- or treadmill-bound and rarely bilateral at the foot. This one is within-subject and longitudinal, outdoors, with both feet and every stream on one clock, built to ask whether your own mechanics drift predicts your breakdown, with chest-strap, phone-GPS and other reference data to check the sensors against.
One 61-minute run at a glance: movement from each LEVEL sensor, heart rate, speed, cadence and relative elevation, all on one clock. Gaps are real dropouts.
Reports
Written-up results live in the companion Space
lvlmotion/running-reports: LEVEL Collector in
the field (capture quality by configuration, fixed and open issues; built from this dataset only),
Methods and literature (why, literature, methods, metric definitions), and one Running with LEVEL
report per participant (measurement specs and results across every run; it also uses that participant's
private context, with their sign-off). Per-session figures are in figures/ here.
The sessions
25 sessions, 1 participant, 11.9 h of recording.
Every run's results, one row each (duration, distance, pace, cadence, contact time, asymmetry, heart
rate), are in each participant's Running with LEVEL report in the
reports Space; the viewer above shows
running.csv, capture.csv and measurements.csv -- what the connected devices recorded.
Every run's figures sit in figures/<subject>/<session>/: overview.png (start there), data-*.png for
each published source as recorded (imu, phone, h10, fit3), derived-*.png for anything computed
from them (spectrum), and analysis-*.png from our running analysis: gait (cadence, ground contact
time, vertical oscillation over the run), foottilt (a 3 s window of foot swing), groundtruth (IMU cadence
against the watch, heart rate and GPS pace, where recorded) and pace (pace and elevation, where GPS was on).
The analysis figures are provisional: the algorithms are not yet validated against a lab reference, and
make_figures.py does not regenerate them. Three catalog files share one row per session, joined on
subject, session: running.csv is the run (conditions, heart rate, cadence, each with its
source), capture.csv is the recording (the setup that was varied, then the capture analysis:
recording length, packet loss, clock alignment, phone and sensor battery and temperature), and
measurements.csv lays what each connected device measured side by side (phone GPS, the watch, the
phone step counter, the chest strap). They hold device data only: no dates, no reported finish times,
no events or places, and no values from our own IMU analysis -- those are in the reports. The column
definitions are in the format spec.
Failures stay in: a chest strap that dropped out, a capture cut short, sensor clocks that did not align.
They are flagged in capture.csv (the analysis columns and the data-quality flags: sensor detached,
clock unreliable, link saturated) and in the figures.
The data
data/<subject>/R01/level/ one folder per session: LEVEL sensor CSVs, chest strap, phone streams, metadata
data/<subject>/R01/fit3/ watch data for the run (where worn)
data/<subject>/R01/survey.csv the participant's survey for the run (where taken and released)
data/context/ per-session conditions, setup and data-quality flags; participant profiles (age group, sex, body-mass band, measured HR max)
data/data_dictionary.md every file, column and unit, and the de-identification policy
figures/ per session: overview.png, data-*.png (as recorded), derived-*.png (computed),
analysis-*.png (running analysis, provisional)
scripts/ lvl_running (iterate / load / plot) + make_figures.py, make_catalog.py
Quick start
# pip install -r scripts/requirements.txt (run from the dataset folder)
import sys; sys.path.insert(0, "scripts")
from lvl_running import iter_sessions, load_session, plot_session
for run_dir in iter_sessions("data"): # every run, all participants and sessions
run = load_session(run_dir) # LEVEL sensors by placement + phone streams + metadata
print(run.name, sorted(run.imus), f"{run.duration_s / 60:.0f} min")
plot_session("data/S01/R01/level", "my_figures") # the same figures as figures/S01/R01/
python scripts/make_figures.py regenerates the overview, data-* and derived-* figures from data/; python scripts/make_catalog.py
regenerates running.csv, capture.csv, measurements.csv and the totals above.
Limitations
- One participant so far, the dataset's author.
- Setups vary between runs on purpose (see
capture.csv); compare runs on the sensors they share. - Consumer references: phone GPS and the phone step counter are convenient, not gold standards; the watch is recorded but is not used as a reference; the Polar H10 is the heart-rate reference.
- Accelerometer range: foot impacts can reach the ±16 g limit, and 100 Hz under-samples the impact
transient (see
derived-spectrum.png); timing-based measures are unaffected.
License and citation
The data and figures are CC BY-NC 4.0 (see LICENSE): free for research and other
non-commercial use with attribution; commercial use reserved. The code in scripts/ is MIT
(see scripts/LICENSE). Copyright Level Health Innovations Corp.
Cite as: Lin, J. (2026). LEVEL Running Dataset. Level Health Innovations Corp. https://huggingface.co/datasets/lvlmotion/running
Built at LEVEL. Jonathan Lin designed, collected and analysed this dataset; the experiment and reporting were built with AI assistance from Claude (Anthropic). Questions and collaboration: jlin@lvlmotion.com
- Downloads last month
- 532
