Diff

baseline p6-36-fill-baseline · c1dba1d637c4 against candidate p6-38-fill-below-reject-line · e59d7823bb29

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

The short answer

The runs first differ at measure, where input frame.json changed.

No stage comes before it. Both stages after it differ.

  1. measureFirst difference
  2. classifyChanged after it
  3. reject_commandChanged after it

Checked from the records. The same answer every time.

What changed between the two runs

The two runs differ.

First difference: stage 1 · measure.

No stage comes before it.

input frame.json changed: e939844ba95e -> 796f68e51892

Both runs' records agree. No recorded setting of measure differs. Its output differs, and all 2 stages after it changed too.

onetrace diff runs/p6-36-fill-baseline runs/p6-38-fill-below-reject-line --text

recorded as a straight line (no graph recorded)

measure · First differencemeasureFirst differenceclassify · Changed after itclassifyChanged after itreject_command · Changed after itreject_commandChanged after it
  1. measureFirst difference
  2. classifyChanged after it
  3. reject_commandChanged after it

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

Settings that changed

No recorded setting differs between the two runs.

The first difference is at stage 1 · measure. No smaller set was reported.

The text diff

Shown with at most 200 lines per output (the SDK's default).

Open the text diff on its own page

first difference: measure — output text changed; settings unchanged; input frame.json changed

measure · First difference

settings: none changed

input frame.json (externally-sourced) changed: e939844ba95e -> 796f68e51892; content not stored

level.json application/json Baseline: verified Candidate: verified

1 line removed · 1 added

11  {
2-   "fill_level_mm": "110"
2+   "fill_level_mm": "70"
33  }

classify · Changed after it

settings: none changed

input level.json (operator-authored) changed: 58a840841536 -> f3f8ab19f47d; content not stored

result.json application/json Baseline: verified Candidate: verified

1 line removed · 1 added

11  {
2-   "result": "pass"
2+   "result": "reject"
33  }

reject_command · Changed after it

settings: none changed

input result.json (operator-authored) changed: 96d76c7af167 -> eb4ba82eee32; content not stored

command.json application/json Baseline: verified Candidate: verified

1 line removed · 1 added

11  {
2-   "command": "none"
2+   "command": "reject the bottle"
33  }

Command: onetrace diff runs/p6-36-fill-baseline runs/p6-38-fill-below-reject-line --text

Repeat this yourself:

onetrace diff runs/p6-36-fill-baseline runs/p6-38-fill-below-reject-line

Other runs that recorded the same value

Matching rule: the same input frame.json digest at stage 1 · measure, by exact equality:
sha256:796f68e51892….sha256:796f68e51892a8a5297b9dcad339478eb31eb8047a26eb62fe5d648cc887806f

1 of 3 stored runs in P6 recorded the same input frame.json digest at stage 1 · measure, the candidate among them.

Nothing here says what the change did in those runs.

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.