Declared synthetic trajectory
This law generates pixels and an independent comparison reference; it is withheld from the estimator.
M010 · Measurement
Record simulated camera pixels, recover derivatives using finite differences or a local fit, then inspect noise, aliasing, calibration bias and integration drift.
Physics tutorial
BackgroundCamera pixels are sampled positions, not direct derivatives.
Why it mattersRecord simulated camera pixels, recover derivatives using finite differences or a local fit, then inspect noise, aliasing, calibration bias and integration drift.
Start with the essentials
This law generates pixels and an independent comparison reference; it is withheld from the estimator.
Scale is pixels per metre; an origin error offsets position but cancels in exact differences.
A smaller time step can amplify the same position error.
Only a complete centered window is used; a wider window also suppresses real rapid motion.
The known added bias illustrates linear drift; it is not inferred camera behavior.
Typical misconceptionEnough frames make numerical acceleration exact.
Better mental modelMore frames reduce the time step and can amplify pixel noise in derivatives. A wider window suppresses noise but also erases rapid motion. At or below twice the declared sinusoid frequency, aliasing is possible; being above that threshold alone does not guarantee an accurate derivative. No confidence interval is claimed.
Acquire Noisy oscillation; open the raw table and export pixels.
What to observe: No true derivative is present in the CSV.Compare three-point differences with a wider quadratic fit.
What to observe: Noise can shrink while rapid motion is lost.Try Aliased motion and Stroboscopic rest.
What to observe: Sparse frames cannot uniquely determine the continuous motion.Change assumed scale, add integration bias, then try Leaves the sensor.
What to observe: Analysis settings preserve raw pixels; missing frames stay missing.