Diff

baseline p1-01-baseline-set1 · 6646490f938c against candidate p1-13-baseline-set1-again · b2b5cd2d9008

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

The short answer

The two runs agree.

  1. load_docsSame
  2. splitSame
  3. embedSame
  4. retrieveSame
  5. answerSame

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)

load_docs · Sameload_docsSameanswer · SameanswerSamesplit · SamesplitSameembed · SameembedSameretrieve · SameretrieveSame
  1. load_docsSame
  2. splitSame
  3. embedSame
  4. retrieveSame
  5. answerSame

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 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/p1-01-baseline-set1 runs/p1-13-baseline-set1-again --text

Repeat this yourself:

onetrace diff runs/p1-01-baseline-set1 runs/p1-13-baseline-set1-again

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.