cert-machine · report · generated from the records

The physics answer key: one hundred simulator runs, two engines, decided in exact arithmetic

A physics engine writes its state as floating-point numbers, and every one of those is an exact fraction. So whether a recorded run kept its energy, to a stated tolerance, can be decided with whole numbers and no rounding in the decision. With Claude (Anthropic’s AI model), I recorded 100 runs of two engines built for simulating robots, MuJoCo 4.0.1 and Newton 1.8.0, on three scenes whose physics is known exactly, and decided each recorded file that way. For MuJoCo, the documentation already describes what the runs show. For Newton, one solver’s default settings include an angular damping that its class description does not mention where it says the method preserves energy. What is added here is the exact decision, the step at which each tolerance first fails, and a page that decides the same bytes again in a browser tab.

−60% −40% −20% 0% 0 2 4 6 8 10 seconds spin energy, change since the start Newton, SolverSemiImplicit at its defaults: −62.7% after 10 s the 8 other configurations of both engines: none more than 2.00% from level
−60% −40% −20% 0% 0 5 10 seconds spin energy, change Newton, SolverSemiImplicit, defaults: −62.7% the 8 others: within 2.00% of level
A flat body tumbling in empty space, with no force and no torque on it, simulated for 10 seconds at a timestep of 0.002 s. Its spin energy should not change. The line that falls is Newton’s SolverSemiImplicit built with every argument at its default, which includes an angular damping of 0.05, a documented default. The grey lines beside the zero line are every other configuration recorded at this timestep. Each curve is drawn from the exactly decided value at every recorded step.Records: certs/physics-key-newton.json · sha256 218f54cb0b95; certs/physics-key.json · sha256 e1d7c3316356The build refuses this figure if a run file is not the pinned bytes, or the record no longer says that the default run loses between 60% and 63% of its spin energy without ever gaining any, or another configuration ends more than 2.5% from level.
recorded runs
100
60 of MuJoCo 4.0.1, 40 of Newton 1.8.0
verdicts
1,464
393 certified, 1,071 refuted, 0 refused
files on which two deciders agree
112 of 112
JavaScript and Python, no shared code, every field
planted files decided as planted
12 of 12
synthetic runs with a known answer

MuJoCo is Google DeepMind’s engine. Newton is a Linux Foundation project initiated by Disney Research, Google DeepMind and NVIDIA. Nothing on this page is a fault report on either: an integrator of finite order is expected to move away from the true motion, and a damping that is a documented argument with a documented default is a choice, not a bug. Each verdict is about one recorded file of bytes, never about an engine in general. The checks are mine, run with Claude (Anthropic’s AI model), which wrote the programs under my direction.

read this first

What is still open

the idea

A float is a fraction

A floating-point number, 64-bit or 32-bit, is a whole number times a power of two. A simulator’s state is a list of them: the time, the positions, the velocities. Kinetic energy and angular momentum are sums of products of those numbers, so for a recorded step they are fractions too, with no error at all. “The energy at step 4,812 is within 1% of the energy at step 0” is then a comparison of two whole numbers.

That removes one layer of doubt. When a floating-point check says an error is 1.9%, the check itself carries rounding. Here the only rounding is the engine’s own, which is the thing being measured. The pendulum needs a cosine, which is not a fraction; it is trapped between two fractions, as tightly as each comparison needs.

the scenes

Three motions with a known answer

the falling body

The speed is right; the position lags

Largest distance between the recorded height and the formula over 2 seconds, rounded up, and the tightest tolerance the whole run stays inside. Four of MuJoCo’s five integrators wrote the same bytes, and so did all four Newton configurations.

MuJoCo 4.0.1, integrator0.01 s0.005 s0.002 s (the default)0.001 s
Euler, implicitfast, implicit, discrete98.1 mm
inside no tolerance tried
49.1 mm
inside no tolerance tried
19.7 mm
inside no tolerance tried
9.82 mm
inside 1 cm
RK42.35 × 10⁻¹⁴ m
inside 1 pm
3.59 × 10⁻¹³ m
inside 1 pm
1.67 × 10⁻¹³ m
inside 1 pm
2.09 × 10⁻¹² m
inside 1 nm
Newton 1.8.0, solver0.01 s0.005 s0.002 s0.001 s
all four configurations (the same bytes)98.1 mm
inside no tolerance tried
49.1 mm
inside no tolerance tried
19.7 mm
inside no tolerance tried
10.1 mm
inside no tolerance tried
  • In MuJoCo, at the default timestep, the body ends 19.7 mm from the formula and first passes 1 cm at step 510. REFUTED at 1 cm; at half the timestep the whole fall stays inside 1 cm.
  • Its speed in MuJoCo is within a billionth of a metre per second at every step of every run. CERTIFIED The step updates the speed first and then moves the body with the new speed, so the position is always one step’s worth ahead: an error that grows in proportion to time and to the timestep.
  • With MuJoCo’s RK4 the position stays within 1.67 × 10⁻¹³ m at the default timestep. CERTIFIED at a millionth of a millionth of a metre.
  • In Newton the position lags the same way: 19.7 mm from the formula at 0.002 s, first past 1 cm at step 511. The speed stays within a millimetre per second at every step of every run CERTIFIED and leaves a micrometre per second by step 87 at every timestep REFUTED: it is at most 342 µm/s off. MuJoCo, which computes in 64-bit floats, holds a billionth on the same law; Newton computes in 32-bit floats.
the pendulum

Energy wobbles, and comes back

Largest change of the total energy over 10 seconds, as a share of the weight times g times the length.

MuJoCo 4.0.1, integrator0.01 s0.005 s0.002 s (the default)0.001 s
Euler, implicitfast, discrete1.85%
inside no tolerance tried
0.920%
inside 1%
0.367%
inside 1%
0.184%
inside 1%
implicit1.85%
inside no tolerance tried
0.920%
inside 1%
0.367%
inside 1%
0.184%
inside 1%
RK41.52 × 10⁻⁸
inside 1 in 10⁶
6.68 × 10⁻¹⁰
inside 1 in 10⁹
1.29 × 10⁻¹¹
inside 1 in 10⁹
7.18 × 10⁻¹³
inside 1 in 10¹²
Newton 1.8.0, solver0.01 s0.005 s0.002 s0.001 s
SolverFeatherstone, defaults; SolverFeatherstone, damping off1.85%
inside no tolerance tried
0.920%
inside 1%
0.367%
inside 1%
0.184%
inside 1%

With MuJoCo’s default integrator at its default timestep the energy is never more than 0.367% from its starting value, and −0.124% at the end. With RK4 it is never more than 1.29 × 10⁻¹¹. Newton’s SolverFeatherstone at the same timestep: never more than 0.367%. It wrote the same bytes with and without the damping argument.

the tumbling body

Some configurations make energy, some lose it, one loses most of it

Largest change of the spin energy over 10 seconds, with the change at the end. No force and no torque act in this scene.

MuJoCo 4.0.1, integrator0.01 s0.005 s0.002 s (the default)0.001 s
Euler9.93% · +9.93% at the end
inside no tolerance tried
4.79% · +4.79% at the end
inside no tolerance tried
1.88% · +1.88% at the end
inside no tolerance tried
0.931% · +0.931% at the end
inside 1%
implicitfast, discrete8.65% · −8.65% at the end
inside no tolerance tried
4.47% · −4.47% at the end
inside no tolerance tried
1.83% · −1.83% at the end
inside no tolerance tried
0.919% · −0.919% at the end
inside 1%
implicit8.65% · −8.65% at the end
inside no tolerance tried
4.47% · −4.47% at the end
inside no tolerance tried
1.83% · −1.83% at the end
inside no tolerance tried
0.919% · −0.919% at the end
inside 1%
RK41.91 × 10⁻⁹ · −4.55 × 10⁻¹⁰ at the end
inside 1 in 10⁶
1.06 × 10⁻¹⁰ · −1.48 × 10⁻¹¹ at the end
inside 1 in 10⁹
2.51 × 10⁻¹² · −1.67 × 10⁻¹³ at the end
inside 1 in 10⁹
1.62 × 10⁻¹³ · −1.47 × 10⁻¹⁴ at the end
inside 1 in 10¹²
Newton 1.8.0, solver0.01 s0.005 s0.002 s0.001 s
SolverSemiImplicit, defaults60.6% · −60.6% at the end
inside no tolerance tried
61.9% · −61.9% at the end
inside no tolerance tried
62.7% · −62.7% at the end
inside no tolerance tried
62.9% · −62.9% at the end
inside no tolerance tried
SolverSemiImplicit, damping off9.94% · +9.94% at the end
inside no tolerance tried
4.83% · +4.83% at the end
inside no tolerance tried
2.00% · +2.00% at the end
inside no tolerance tried
1.16% · +1.16% at the end
inside no tolerance tried
SolverFeatherstone, defaults; SolverFeatherstone, damping off9.93% · +9.93% at the end
inside no tolerance tried
4.79% · +4.79% at the end
inside no tolerance tried
1.88% · +1.88% at the end
inside no tolerance tried
0.930% · +0.930% at the end
inside 1%
−2% −1% 0% +1% +2% 0 2 4 6 8 10 seconds spin energy, change since the start Euler, the engine’s default: +1.88% after 10 s implicitfast, the one its documentation recommends: −1.83% RK4: never more than 2.51 × 10⁻¹² away
The same scene on a much finer scale, MuJoCo only, at its default timestep of 0.002 s: the three behaviours of its integrators.Record: certs/physics-key.json · sha256 e1d7c3316356The build refuses this figure if a run file is not the pinned bytes, or the record no longer says that the Euler run gains energy at its first step and that the implicit runs never gain any.
  • MuJoCo, Euler (its default). The spin energy rises at the first step of every run and ends at its largest value: +1.88% at the default timestep. The largest rise within one step is 0.00220% of the starting energy.
  • MuJoCo, implicitfast, implicit and discrete. The spin energy falls: −1.83% at the default timestep, −8.65% at 0.01 s, −4.47% at 0.005 s, −1.83% at 0.002 s, −0.919% at 0.001 s.
  • MuJoCo, RK4. Never more than 2.51 × 10⁻¹² from the start at the default timestep.
  • Newton, SolverSemiImplicit at its defaults. The spin energy falls at every timestep: −60.6% at 0.01 s, −61.9% at 0.005 s, −62.7% at 0.002 s, −62.9% at 0.001 s. “Within 1% of its starting value” first fails within 0.11 s of the start in every run. REFUTED “Never rises” holds at every step of every run, with no tolerance. CERTIFIED
  • Newton, SolverSemiImplicit with the damping off. The spin energy rises, as under MuJoCo’s Euler: +9.94% at 0.01 s, +4.83% at 0.005 s, +2.00% at 0.002 s, +1.16% at 0.001 s (MuJoCo’s Euler: +9.93%, +4.79%, +1.88%, +0.931%).
  • Newton, SolverFeatherstone. The same bytes with the default damping and with the damping off, at every timestep. The spin energy rises: +9.93% at 0.01 s, +4.79% at 0.005 s, +1.88% at 0.002 s, +0.930% at 0.001 s.
  • Angular momentum changes with the energy, with no torque acting. At the timestep 0.002 s its squared size ends +1.88% under MuJoCo’s Euler, −1.83% under implicitfast, and −62.7% under Newton’s SolverSemiImplicit at its defaults.
a published sentence, decided

The documentation’s own property holds exactly

The kinetic energy of a spinning free body is non-increasing in the absence of applied force. Steady spins about principal axes are conserved almost exactly; tumbling motion is mildly damped […]. Systems requiring long-horizon energy conservation of tumbling bodies should use the RK4 integrator.MuJoCo documentation, Computation, Numerical integration, “Gyroscopic derivatives for free bodies”, read 17 November 2026
a second published sentence

A sentence and a default

Semi-implicit time integration is a variational integrator that preserves energy, however it not unconditionally stable, and requires a time-step small enough to support the required stiffness and damping forces.Newton 1.8.0, the class description of SolverSemiImplicit and, in the same words, of SolverFeatherstone; quoted as written
written before running

What I expected, and where I was wrong

how it was checked

Rules first, two deciders, planted files

who did what

Each part is someone’s

check it yourself

How to re-run it

contact

Write to Carlos

Sent by Web3Forms to Carlos’s inbox; nothing stored here.

Or write to carlos@carlostoledo.co, or open the public pilot form on GitHub.