Versions and provenance
What is versioned
| item | where | meaning |
|---|---|---|
| engine version | dtta.__version__ (0.1.0) |
the software build; stamped into every artifact and into the session record |
| algorithm version | ParamSet.algorithm_version (1) |
bumped whenever any frozen parameter or algorithm behaviour changes |
| parameter set id | ParamSet.param_set_id (v1-default) |
the frozen constant set; the full dictionary is copied into every artifact |
| stage algorithm strings | e.g. speed-1.0.0, delta-1.0.0, imu-1.0.0+mount-1.0.0 |
per-stage implementation version in each artifact's provenance |
| centerline version | hash of the centerline artifact | an input of every downstream artifact |
| telemetry identity | gpmd_sha256 per chapter, session_id = hash of the chapter hashes |
the authoritative identity of the data; a video re-uploaded under another name yields the same session |
Invalidation
An artifact is stale when any of algorithm version, parameter-set id, parameter hash or input hashes differs. The video file's fingerprint never invalidates telemetry artifacts.
Reading the Provenance tab
For the analysis on screen it lists: engine version, parameter set and algorithm version, the camera (model, firmware, GPS stream and rate, IMU rate), each chapter's telemetry hash, one row per stage with its algorithm string, inputs, units and notes (e.g. the actual filter rates used), the endpoint-invariant error of every lap pair, and the run log with timestamps.
Reference tables (generated from the engine)
- Parameter set — every constant with its value and meaning.
- Metric reference — every number the interface can show.
- GPS flags and stage algorithms.
These files are written by dtta methodology export from the same registry the API serves; a unit
test fails when they drift from the code.