Skip to content

1.8.0 — group QoM returns a different number, and the old one was confounded

Choose a tag to compare

@alexarje alexarje released this 05 Aug 14:44
· 36 commits to master since this release
c03fbab

group_qom, pose_qom and normalized_qom return different numbers. They are re-exported from micromotion, which released 1.0.0 today, and this is a correctness fix rather than a refinement.

They averaged over every marker at every frame while the underlying band_limited_qom interpolates gaps, so an occluded marker contributed a near-zero speed and still counted in the divisor. The result tracked how much the cameras saw rather than how much the body moved.

Twelve markers with a realistic dropout pattern, a median of eight visible: 78.07 against a true 91.53, with the speed series correlating +0.246 with the per-frame count of visible markers. The new default, normalize="visible", gives 90.85 at −0.001.

Pass normalize="worn" to reproduce a figure published with an earlier release, and say which you used. Clean pose data with no dropouts is unaffected; occluded mocap is affected most.

The micromotion floor is now >=1.0.0. That is a correctness floor rather than a documentation one: below it the re-exported function returns the confounded number.

All 545 tests pass against micromotion 1.0.0 unchanged, which also means none of them covered the behaviour that changed. The occlusion tests live upstream.