Reading Results

evaluate() returns an EvalRunResult — a summary per metric, one result per case, and where the run reported.

Summary

summary() prints one line per metric:

matches_expected: mean=0.75 pass=3/4 count=4

A boolean score passes or fails on its own value. A numeric score needs a threshold to be judged — without one it’s averaged, and pass=k/n is left off.

Python
TypeScript

result = evaluate(name="weather", dataset=ds, task=task, scorers=[reports_temp])
print(result.summary())

const result = await evaluate({ name: "weather", dataset: ds, task, scorers: [reportsTemp] });
console.log(result.summary());

Token counts and cost aren’t in the local summary — the platform prices them from the run’s spans and shows them in the UI.

Per-case results

Python
TypeScript

for item in result.results:
    print(item.case_id, item.output, item.scores)

for (const item of result.itemResults) {
  console.log(item.caseId, item.output, item.scores);
}

Each item carries case_id, input, output, expected, scores, trace_id, duration_ms, and any error or scorer_errors. A case that hit an error is errored; use case_status(item) / caseStatus(item) to check. The run also exposes counts (case_count, errored, not_scored), the candidate_version it was labelled with, upload_state with the run’s dashboard_url, and dataset — the exact dataset version the run measured.

Evaluation run results table with each case's input, output, expected value and scorer columns — Evaluation run: each case's input, output, expected answer and scores

Upload later

Save a run and upload it afterwards, for when the run happens somewhere without credentials.

Python
TypeScript

from traceroot import EvalRunResult

result.save("run.json")

later = EvalRunResult.load("run.json")
later.upload()

import { EvalRunResult } from "@traceroot-ai/traceroot";

result.save("run.json");

const later = EvalRunResult.load("run.json");
await later.upload();

upload() rebuilds the reporting destination from the saved run, and keeps its scorers’ thresholds — so a later upload records the same pass and fail results as the original run.

Reading a run later

EvalRunResult is what the process that ran the eval holds. Once the run has reported, the CLI reads it back from anywhere — including a run somebody else started.

traceroot evals runs list --evaluation-id ev_…   # find the run id
traceroot evals runs get run_…                   # counts, per-scorer means, cost and duration

Next steps

From the Terminal

Read datasets, evaluations, and past runs with the CLI.

Running Evals

Every option of evaluate(), and where a run reports.

Datasets

Pull a dataset version to reproduce a past run.

Overview

Tracing

CLI

Detectors

Signals

Alerts

Evaluations

Dashboards

TraceRoot Agent

Summary

Per-case results

Upload later

Reading a run later

Next steps

From the Terminal

Running Evals

Datasets

​Summary

​Per-case results

​Upload later

​Reading a run later

​Next steps

From the Terminal

Running Evals

Datasets

Summary

Per-case results

Upload later

Reading a run later

Next steps