Noveum docs
ProductsNovaSynthRun tests and review resultsCompare results in Analytics

Analytics

Compare NovaSynth pass rates across batches, coverage, persona and scenario trends, and scorer failures.

Open NovaSynth → Analytics after runs and their linked eval-job scoring complete. Analytics compares batches over a date range and applies each batch's critical scorers to its pass-rate views.

Choose the date range

Open Analytics and choose Last 7d, Last 30d, Last 90d, or All at the top of the page. The page opens on Last 30d.
Confirm that the range contains both the baseline batch and the newer batch you intend to compare.
Check the evaluated and total run counts on each batch before interpreting its pass rate.
Use the comparison and trend cards to narrow the change to a batch, persona and scenario pairing, or scorer.
Open the relevant batch and individual runs to verify the transcript and scorer evidence behind the aggregate.

The range applies to Pass Rate Trend Across Recent Batches, Batch Comparison, the persona and scenario trend, the scorer trend, Top Failing Scorers, and the CSV export. Scenario Coverage and Persona Coverage always count every run in the project.

Pass rates

NovaSynth reports two pass rates for evaluated runs:

  • Pass Rate counts a run when every critical scorer scores 7 or higher with no scorer error.
  • 70%-Criteria Pass Rate counts a run when at least 70% of its critical scorers score 7 or higher and none is unavailable. Comparison and trend cards label this rate Critical Success Rate.

Critical scorers are the ones starred when the batch was created. When a batch has no critical scorers, every scorer it ran counts. Runs without completed scorer results are excluded from both rates. See Choose scorers.

Cards

CardWhat it answers
Pass Rate Trend Across Recent BatchesHow did the pass rate and the 70% threshold rate move from batch to batch? Only batches with evaluated runs appear. Hover a batch to see its evaluated and total runs.
Batch ComparisonHow do two to four chosen batches differ on Pass Rate, Total Runs, Personas, Scenarios, Criteria Met, Critical Success Rate, Avg Duration, and Total Duration?
Scenario Coverage and Persona CoverageWhich scenarios and personas are the most and least tested, with run counts and average duration?
Persona × Scenario Critical Success Rate TrendHow did one persona and scenario pairing perform across batches?
Scorer Critical Success Rate TrendHow often did one scorer pass in each batch that ran it?
Top Failing ScorersWhich critical scorers fail most often? Up to ten scorers appear, ordered by failure rate.

Compare batches

In Batch Comparison, click + Add Batch and search for a batch.
Add a second batch. The comparison table appears once two batches are selected, and you can add up to four.
Read the delta column, which compares the first selected batch with the last.
Remove a batch with its chip to swap in a different one.

Criteria Met counts passing scorer results out of all scorer results in the batch, so it shows how close a failing batch came to passing.

Follow a pairing or scorer

Persona × Scenario Critical Success Rate Trend starts on the first persona and scenario. Choose another Persona: and Scenario: to plot that pairing's critical success rate for each batch that evaluated it, with the criteria met for each point.

Scorer Critical Success Rate Trend starts on the first scorer. Choose another Scorer: to plot, for each batch that ran it, how many runs that scorer passed. Scorer errors count toward the batch total but not toward passes.

Coverage

The coverage cards list the top five scenarios and personas. Switch between Most tested and Least tested, or click View all to search the full list.

Read the page in order

  1. Validate the population. Check the date range and each batch's evaluated and total runs. A low evaluated count can make a pass-rate change look more significant than it is.
  2. Locate the change. Use Pass Rate Trend Across Recent Batches to find when quality moved, then compare the batches on either side in Batch Comparison.
  3. Check coverage. Use the coverage cards to confirm that both batches exercised comparable scenarios and personas.
  4. Isolate the behavior. Use the persona and scenario trend and the scorer trend to find which pairing or criterion changed.
  5. Find the failing behavior. Use Top Failing Scorers, then open the batch and individual transcripts for evidence.

Analytics is a comparison surface, not a substitute for run inspection. A scorer failure can have different causes across two transcripts even when it contributes to the same aggregate.

Empty cards

An empty card does not always mean there are no runs:

  • Pass-rate cards require completed scorer results.
  • The persona and scenario trend needs completed runs for the chosen pairing.
  • Top Failing Scorers appears only when scorer pass or fail data is available.
  • A shorter date range may exclude batches that are visible on the Runs page.

If a batch has runs but no evaluated runs, open an individual run and check its analysis status and linked eval-job scorer results. Then confirm that the batch marked the scorers you intend to aggregate as critical.

Export CSV

Click Export CSV to download novasynth-analytics.csv for the selected range. The file contains these sections:

  • pass rate by date;
  • run counts by scenario category;
  • the five newest batches in the range with their pass rate, evaluated runs, and total runs;
  • average duration and run count by endpoint;
  • every batch in the range with its date, pass rate, 70%-criteria pass rate, evaluated runs, and total runs.

Column headings follow the current interface language. Export after choosing the intended date range. The CSV reflects that range and does not include the coverage cards.

Use analytics for regressions

Run a stable persona-scenario set against the current deployment.
Record the batch's pass rate, 70%-criteria pass rate, and leading failing scorers.
Deploy one focused prompt, model, tool, or infrastructure change.
Duplicate or recreate the same batch against the updated deployment.
Add both batches to Batch Comparison and review the deltas before expanding the change.