01.2 / RUN COMPARISON

Compare before guessing.

Choose a successful baseline, check the test conditions, and inspect what changed. The engineer decides what to investigate.

SYNTHETIC · WORKING PROTOTYPERobot 01 / Configuration comparison
SUCCESSFUL BASELINE · RUN-04210 / 10 pickssnap-042 · revision 1
FAILURE · RUN-0434 / 10 pickssnap-043 · revision 1
6 recorded changes1 unknown comparisons

Showing 10 of 10 fields. Select a field name to inspect its evidence.

On narrow screens, scroll the table horizontally to see both runs and the result.

Recorded values from run-042 and run-043; all values are synthetic.
Configurationrun-042 · Baselinerun-043 · Selected runResult
Manually reportedG-01 · revision AG-02 · revision BChanged
a31c9e2000000000000000000000000000000000 · cleanf72b4d1000000000000000000000000000000000 · cleanChanged
gripper-fw-1.8gripper-fw-1.9Changed
pick-policy-v3pick-policy-v4Changed
teleop-block-A-v12teleop-block-A-v13Changed
camera-cal-07camera-cal-08Changed
Unknown — Force was not recordedUnknown — Force was not recordedUnknown
pick-v2pick-v2Unchanged
Pick block-APick block-AUnchanged
22 °C · 0.25 m/s22 °C · 0.25 m/sUnchanged

Changes are starting points, not proven causes. Missing values remain unknown. These invented runs demonstrate the actual comparison engine; no customer results are shown.

Inspect the example’s context and provenance

Baseline run-042 is fixed for this illustration; choose your own baseline in the full demo. Each run references the exact snapshot revision shown above. All entries were manually supplied by “Demo operator.”

Baseline observed: 2026-09-01T09:00:00Z; recorded: 2026-09-01T09:02:00Z. Selected hardware observed: 2026-09-01T10:00:00Z; recorded: 2026-09-01T10:02:00Z.

Evidence references and underlying model/dataset artifacts are unavailable. Versions identify recorded references, not verified artifact contents. No cause or resolution is confirmed.

Inspect each field and its provenance →

Differences are a starting point.

The example above uses invented records and the working comparison engine. Missing evidence never proves sameness. Changes in procedure or conditions limit how a comparison can be interpreted.

Keep the setup that worked

The full demo includes a successful run’s exact snapshot reference and an engineer-led recreation checklist. Verify artifacts, confirm physical hardware, and retest through your existing process.

Tav does not diagnose a cause or deploy and roll back robot changes.

Open the full working demo ↗
Meet Tav
A good place to start

Curious about Tav?

Explore an example or talk through your workflow with the founders.

Book a demo ↗Explore the synthetic demo →Demo & contact guide · Not a live chat