Diff

baseline p5-32-pump-baseline · 418cab89c192 against candidate p5-34-pump-firmware-changed · 1db868b24ec9

Both runs' records agree. Every check behind this is on Proof

The short answer

Every recorded output is the same. A setting differs: sensor_firmware at readings, 3.1 → 3.2.

  1. readingsSame
  2. calibrateSame
  3. featuresSame
  4. anomaly_checkSame
  5. decisionSame
  6. work_orderSame

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)

readings · SamereadingsSamesensor_firmware 3.1 →…sensor_firmware 3.1 → 3.2decision · SamedecisionSamecalibrate · SamecalibrateSamework_order · Samework_orderSamefeatures · SamefeaturesSameanomaly_check · Sameanomaly_checkSame
  1. readingsSamesensor_firmware 3.1 → 3.2
  2. calibrateSame
  3. featuresSame
  4. anomaly_checkSame
  5. decisionSame
  6. work_orderSame

A link shows which recorded output a stage read. It does not by itself prove that one stage caused the next.

Settings that changed

StageSettingBaselineCandidate
readingssensor_firmware3.13.2

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/p5-32-pump-baseline runs/p5-34-pump-firmware-changed --text

Repeat this yourself:

onetrace diff runs/p5-32-pump-baseline runs/p5-34-pump-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.