Most of the validation work on vaas-x so far had been industrial sensor data — turbofans, machine telemetry.
I wanted to know if the same zero-config channel classifier actually transfers to a completely different domain: a wearable IMU strapped to a moving human.
No feature engineering, no per-sport tuning, no hints about what any channel means.
I'm writing this one up slightly differently than my other posts, because the first version of this test gave me a wrong answer, and I think the reason it was wrong is more useful than the result itself.
The dataset UCI's Daily and Sports Activities set (Altun, Barshan & Tunçel, 2010): 8 subjects, each wearing five Xsens IMU units — torso, both arms, both legs — 9 axes per unit (accelerometer, gyroscope, magnetometer × x/y/z), sampled at 25Hz. 45 channels total.
It includes both a sedentary activity (sitting) and dynamic sport activities (basketball, rowing), which gives a clean, checkable question: does a classifier that's never seen this data correctly tell apart "person sitting still" from "person playing basketball," using channel statistics alone?
First attempt — and the mistake My first pass pooled all 8 subjects together per activity and ran it through the profiler in one shot.
The result came back backwards: sitting showed up with more "significant" channels than basketball.
That's not just unexpected, it's physically nonsensical — a person sitting still should be one of the lowest-variance activities in the entire dataset.
The bug wasn't in the classifier.
It was in the test.
Pooling subjects together means each subject's own sensor baseline and IMU orientation differences get mixed into the between-subject variance for every channel — including sitting, where there's no real movement to swamp that noise.
For basketball, the actual movement signal is large enough to dominate regardless.
Pool the data and you're accidentally measuring "how different are these 8 people's resting sensor baselines" more than "how much does this channel move during this activity." The fix: one continuous stream per subject, per activity That's also just what a real deployment looks like — one wearable, one athlete, one continuous stream.
So I reran it that way: for each of the 8 subjects independently, feed their sitting stream and their basketball (or rowing) stream through the profiler as two separate single-device sessions.
The result, once the methodology was fixed Across all 8 subjects, sitting left an average of 14.8 of 45 channels classified stable, 22.4 flagged significant.
Basketball and rowing collapsed to zero stable channels in every single subject, with 40–44 of 45 flagged significant every time.
Consistent, in the right direction, in all 8 people — with no channel labels or activity hints ever given to the classifier.
Check it against something outside the SDK entirely Plain pandas , nothing from the SDK.
Basketball came out roughly 154x higher variance than sitting, rowing roughly 27x — computed completely independently of whatever the classifier decided.
The classifier's "significant vs. stable" split is tracking a real, independently measurable physical signal, not an artifact of how it happens to score things.
What this doesn't show I want to be as clear about this here as the whitepaper is: this validates that zero-config channel profiling correctly separates a sedentary activity from a dynamic one, on real wearable data, in a domain the classifier was never tuned for.
It does not validate injury prediction, movement-quality scoring, or that a flagged pattern means anything clinically.
That's a much harder, differently-evidenced claim, needs labelled injury-outcome data specific to a sport and population, and I haven't tested it — so I'm not claiming it.
The mistake in my first pass is the part I'd actually want another engineer to take away from this: pooling data across subjects/devices/sessions before checking a per-entity classification claim is an easy way to quietly valida