Motion smoothness metrics
Motion smoothness metrics are scores that measure how smoothly a movement unfolds, computed from a speed or acceleration signal. Common ones are jerk, the rate of change of acceleration, log dimensionless jerk (LDLJ), which normalizes jerk for duration and amplitude, and spectral arc length (SPARC), which measures how spread out a movement's frequency content is. In robot learning, they help rank demonstrations and rollouts for review, but they measure the motion, not whether the task succeeded.
Building visual or physical AI?
Let's talk.
What are motion smoothness metrics?
Key takeaways
- Jerk, LDLJ, and SPARC each score a different aspect of how smoothly something moved.
- LDLJ and SPARC are dimensionless, so you can compare movements of different lengths and sizes.
- Smoothness measures the motion, not the outcome, so a smooth episode can still fail its task.
How it works
- Jerk is the third derivative of position, or how fast acceleration changes. Jerk RMS reports it in physical units, which helps find a local rough spot but makes movements of different sizes hard to compare.
- Log dimensionless jerk (LDLJ) integrates squared jerk over the movement, scales it by the movement's duration and peak speed so the result has no units, then takes the logarithm. Values are negative, and more negative means less smooth.
- Spectral arc length (SPARC) takes the Fourier magnitude spectrum of the speed profile, normalizes it, and measures the length of that curve up to an adaptive cutoff frequency. A single smooth movement keeps its energy at low frequencies and gives a short arc. Corrections and tremor add higher-frequency content and lengthen it. Values are negative, and more negative means less smooth.
Plot the speed trace, then check what the rough spots really were
- rough speed traces that are really a regrasp, not a bad motion
- rough scores caused by a sensor dropout, not by the motion
- short episodes, where a sliding window has too few samples to score reliably
Robotics Droid
1,000 episodes
Real-world robot manipulation episodes from DROID, stored as MCAP with three synced cameras and fields for task prompt, success, and number of grasps.
Try this: Filter num_grasps to 3 or more, open an episode, and find the stops and restarts in its end-effector speed signal.
Free with a work or .edu email.
Go deeper
- Motion Smoothness Doesn't Predict Robot Task Success: RoboLab-EgoX
- Smooth Isn't the Same as Correct: Triaging Robot Episode Quality with FiftyOne
- Everyone Is Scoring Robot Data, Nobody Is Looking at It: Mapping the Robot Data Quality Stack
- You Can’t Watch 10,000 Episodes. Measure These Instead: Curation Metrics for LeRobot Datasets
Why it matters
Frequently asked questions
What is log dimensionless jerk?
What is spectral arc length (SPARC)?
Does a smoother robot episode mean a better demonstration?
Related terms
