Motion Repair · BrokenAMASS

Paired restoration quality for corrupted SMPL motion. The public population keeps clean GT, corrupted input, and every repaired result synchronized in one interactive 3D comparison.

299 paired cases 100 frames · 20 fps SMPL-22 geometry uTMR-first ranking Physical diagnostics
Current public snapshotLoading verified results
Repair methods
3
MoGenDiT, StableMotion, MotionCanvas
Best uTMR R@3
–
Generated methods only
Lowest MPJPE
–
Generated methods only
Visual population
299
Five synchronized SMPL views per case

Method comparison

uTMR semantic preservation is the primary ranking view; geometry and physical metrics remain selectable.

Best generatedSecond generatedGT / input

uTMR R@3

Higher is better; references are excluded.

Normalized profile

100 is the best generated value on each axis; reference rows are excluded.

All-case motion comparison

Inspect Clean GT, the corrupted input, and all three repair outputs in synchronized, orbitable SMPL mesh views.

299 cases · 5 views
Clean GT + corrupted source + three repairsCorruption recipes · synchronized playback

Complete results

GT is pinned first, followed by the corrupted input; generated methods default to uTMR R@3 order.

3 methods + input + GT
uTMR operates on canonical SMPL-22 joint positions.Support tracks are shown explicitly and are not silently pooled.
Protocol details

Paired population

All methods use the same 299 pair-validated BrokenAMASS clips, fixed to 100 frames at 20 fps in right-handed Z-up metres.

Support tracks

MoGenDiT uses its method-native adaptive estimate. StableMotion and MotionCanvas use the same oracle-v6 support contract. The table never hides this distinction.

Primary evaluator

uTMR R@3 is the default sort. MPJPE, global-boundary MPJPE, root error, acceleration error, skating, penetration, and jitter are paired diagnostics.