kartnet

KartNet v3 — track-specialized telemetry from onboard karting video

KartNet turns onboard video from one specific indoor kart circuit (Racehall Aarhus, Denmark) into telemetry that no sensor can record there — GPS does not work indoors:

• speed (m/s, per frame at 10 Hz)
• track position — where on the lap the kart is, as a cyclic phase; lap times fall out of the wrap points
• yaw rate

If the recording carries an IMU (DJI and GoPro action cameras embed one), an optional input branch uses it and measurably improves accuracy. Without sensors the model runs on video alone — one checkpoint serves both cases.

It is the specialized sibling of SpeedNet, our general ego-speed model. Where SpeedNet must work on any road, KartNet exploits the fact that every clip shows the same 790 m circuit — which buys per-frame position and much tighter speed.

Demo

Held-out race (never trained on), same venue, video + IMU. The speed readout and the lap-position bar are model outputs; there is no GPS in the loop anywhere:

<video src="https://huggingface.co/x2q/kartnet/resolve/main/assets/demo.mp4" controls muted playsinline width="100%"></video>

How it was trained — labels without any ground truth sensor

There is no GPS indoors and rental karts expose no data bus, so the training labels themselves had to be manufactured from video:

1. Corpus self-localization. 29 hours of onboard footage from the same circuit (76 recordings: different drivers, karts, cameras, seasons, lighting) were all aligned to a single canonical reference lap with a cyclic Viterbi over frame-signature similarity. Every frame gets a position u around the lap.
2. Lap times for free. Laps are the wrap points of u. Validated against lap times published in video titles (median error 0.22 s) and against the venue's official SMS-Timing for one race (27/27 laps, median error 0.19 s) — data the aligner never saw.
3. Metres from physics. The advertised track length (1000 m) is the centreline; a racing line cuts corners, and three independent estimates (corner-cut geometry, integrated flow speed, the karts' rated top speed) agree on ~790 m driven per lap. Speed is then 790 m x du/dt.
4. Result: 809 laps / 748k frames with per-frame speed, position and yaw labels — from video alone.

Evaluation

Held-out whole videos (unseen sessions, drivers, karts, lighting):

Length-invariance (the model was trained with randomized sequence lengths, so window size is a throughput knob, not an accuracy mode):

Does it measure, or does it recall? A model that can localize itself on a known track could fake speed by recalling what karts usually do at that corner. Ablation says no:

Appearance refines; optical flow carries the measurement.

Cross-camera holdout — a different camera, mount and month (a DJI helmet camera never seen in training except via two other sessions from the same device), judged against official race timing:

Limitations — read before use

• One venue, one layout. This model is Racehall Aarhus in its standard direction, by design. Other tracks, or this track in reverse layout, produce garbage positions (our own reverse-layout footage is correctly rejected by the label pipeline, but the model has no such guard).
• Lap times from the position head are unreliable on unfamiliar cameras. On the cross-camera holdout the phase runs fast and reads lap times ~5 s short despite good median position. If you need lap timing on a new camera setup, derive it from signature alignment against a reference lap instead — or fine-tune.
• Absolute speed scale is ±5%. The 790 m driven-lap length is derived, not surveyed.
• Frame-level dynamics carry label noise. Within-lap timing of accel/brake transitions inherits smoothing from the auto-labels (~0.7 s); per-lap statistics are much tighter than per-frame values.
• The vibration IMU channel needs the full-rate (≥50 Hz) accelerometer stream; feeding downsampled IMU zeroes its benefit.

Model details

• 1.67 M parameters: flow CNN (4 blocks → 256-d) + appearance CNN (4 blocks → 128-d) + IMU MLP (5 channels + presence flag → 32-d) → 2-layer GRU (256) → three linear heads.
• Inputs at 10 Hz: Farneback flow 128×72 (decoded at 30 fps, every 3rd frame kept), grayscale 128×72, optional IMU (g_lon, g_lat, yaw/60, |a|−1, vibration RMS).
• Camera-robustness training: random zoom/translation with consistently scaled flow vectors, resolution degradation, photometric jitter, appearance dropout (25%), IMU dropout (40%), randomized sequence lengths (16/32/64/128).
• Training data is not redistributed: most of the corpus is publicly posted third-party onboard footage, used for training only. This repository contains weights, code and documentation — no footage.

Quickstart

Fetch the repo via huggingface_hub rather than downloading the weight file directly — this is also what makes your download count toward the model's stats on the Hub:

from huggingface_hub import snapshot_download
local_dir = snapshot_download("x2q/kartnet")

import torch
from modeling_kartnet import KartNet, extract_features, predict

model = KartNet()
model.load_state_dict(torch.load("kartnet_v3.pt", map_location="cuda"))

feats = extract_features("onboard.mp4")     # ffmpeg + OpenCV, ~2x realtime
out = predict(model, feats, device="cuda")

out["speed_mps"]       # per-frame speed, 10 Hz
out["u"]               # lap phase in [0,1)
out["lap_times_s"]     # from phase wrap points

With IMU (example for DJI embedded telemetry, any source works if timestamps are on the video clock):

from modeling_kartnet import imu_features
imu = imu_features(len(feats["gray"]), t_imu, accel_xyz_g, yaw_rate_dps,
                   gforce_lon, gforce_lat)
out = predict(model, feats, imu=imu, device="cuda")

Or just: python example.py my_clip.mp4

License

Apache-2.0 (weights and code).

Citation

@misc{kartnet2026,
  title  = {KartNet v3: track-specialized telemetry from onboard karting video},
  author = {x2q},
  year   = {2026},
  url    = {https://huggingface.co/x2q/kartnet}
}