A peak is not an average.
Record what the number represents.
Keep the measurement window, direction of movement, reset handling, policy and environment beside the result. The command sent to a policy is also different from the speed observed.
The evaluation version matters.
The evaluation script at the reviewed submodule commit reports displacement over a time window. It does not implement the upright-gated instantaneous peak described in the project log.
Inspect the reviewed evaluation code ↗Reproducing the reported peak requires its matching evaluation version and checkpoint. These values are not verified hardware performance.
What would you like to understand next?
Keep the source, your environment and your observations together.
Before you continue
Can the reported peak speed replace average speed?
No. Keep the measurement window, reset handling and upright condition with each value. These DuckEMW figures describe author-reported simulation.
Applies to: DuckEMW · emwstudio. Keep the model, image, software and driver versions together. The dated sections below retain their original verification limits.
Source checked:
Next useful guides
DuckEMW: MicroDuck Sprint & Dance Simulation Project
Explore emwstudio’s DuckEMW sprint and dance simulation project, with pinned source revisions, measurement notes and clearly stated verification limits.
DuckEMW Dance Timeline: Beats, Moves & Policy Playback
Read DuckEMW dance timeline source notes: tempo, first-beat offsets, movement segments and policy compatibility for MicroDuck simulation.
MicroDuck Simulator: First Walk and Public Move Loading
Walk in the official MicroDuck browser simulator, load a public policy by URL, check manifest compatibility and restore the built-in move.