Diff
baseline p9-46-torque-baseline · d88f256424e0 against candidate p9-47-torque-tool-firmware-changed · 389d15ee276c
Both runs' records agree. Every check behind this is on Proof
The short answer
Every recorded output is the same. A setting differs: tool_firmware at read_tool_log, 4.2 → 4.3.
- read_tool_logSame
- torque_checkSame
- station_decisionSame
Checked from the records. The same answer every time.
What changed between the two runs
The two runs do not differ.
recorded as a straight line (no graph recorded)
- read_tool_logSame
tool_firmware 4.2 → 4.3
- torque_checkSame
- station_decisionSame
A link shows which recorded output a stage read. It does not by itself prove that one stage caused the next.
Settings that changed
| Stage | Setting | Baseline | Candidate |
|---|---|---|---|
| read_tool_log | tool_firmware | 4.2 | 4.3 |
The report names no localized set. That is what it says, not a gap in this page.
The text diff
Shown with at most 200 lines per output (the SDK's default).
no difference: every stage is the same
Command: onetrace diff runs/p9-46-torque-baseline runs/p9-47-torque-tool-firmware-changed --text
Repeat this yourself:
onetrace diff runs/p9-46-torque-baseline runs/p9-47-torque-tool-firmware-changed
Other runs that recorded the same value
The two runs do not differ, so there is no changed value to look for.
What may have happened
This demo kept no explanation of this comparison.
This record shows what was verified and evaluated at the time — not what was ultimately true.