- Getting noisy or inconsistent scores? Measure variance with trials.
- No expected outputs to compare against? Iterate with hill climbing.
- Evaluating images, audio, or PDFs? Add attachments.
- Eval running slowly or throwing errors? Trace and debug your task.
- Iterating locally and don’t want to save runs? Run without uploading results.
Eval() function. See Run experiments in code to get a basic eval running first.
Measure score variance with trials
Run each input multiple times to measure variance and get more robust scores. Braintrust intelligently aggregates results by bucketing test cases with the sameinput value:
Override trial count per case
Individual data rows can set their own trial count to override the global default. Use this when a few inputs need extra trials to measure variance, while the rest don’t:trialCount / trial_count / TrialCount. If neither is set, the input runs once.
Iterate without expected outputs
Hill climbing lets you improve iteratively without expected outputs by using a previous experiment’soutput as the expected for the current run. To enable it, use BaseExperiment() in the data field. Autoevals scorers like Battle and Summary are designed specifically for this workflow.
expected field by merging the expected and output fields from the base experiment. If you set expected through the UI while reviewing results, it will be used as the expected field for the next experiment.
To use a specific experiment as the base, pass the name field to BaseExperiment():
- Non-comparative methods like
ClosedQAthat judge output quality based purely on input and output without requiring an expected value. Track these across experiments to compare any two experiments, even if they aren’t sequentially related. - Comparative methods like
BattleorSummarythat accept anexpectedoutput but don’t treat it as ground truth. If you score > 50% on a comparative method, you’re doing better than the base on average. Learn more about how Battle and Summary work.
Evaluate images, audio, and PDFs
Braintrust allows you to log binary data like images, audio, and PDFs as attachments. Use attachments in evaluations by initializing anAttachment object in your data:
Trace and debug your eval tasks
Add detailed tracing to your evaluation task functions to measure performance and debug issues. Each span in the trace represents an operation like an LLM call, database lookup, or API request.Use
wrapOpenAI/wrap_openai to automatically trace OpenAI API calls. See Trace LLM calls for details.traced() to log incrementally to spans. This example progressively logs input, output, and metrics:
Troubleshooting
Evaluations running slowly with maxConcurrency
Evaluations running slowly with maxConcurrency
If your evaluations are slower than expected when using
maxConcurrency, you may be on an older SDK version that flushes logs after every single task completion. Upgrade to TypeScript SDK v3.3.0+ for up to an 8x performance improvement. The SDK now uses byte-based backpressure for better flushing performance.You can tune the flush threshold with the BRAINTRUST_FLUSH_BACKPRESSURE_BYTES environment variable. See Tune performance for all available configuration options.Task function throws an exception during eval (C# SDK v0.2.2+)
Task function throws an exception during eval (C# SDK v0.2.2+)
When the task function throws, the C# eval framework catches the exception, records it on the task span and root span (with The task span and root eval span both receive an OTel exception event with
ActivityStatusCode.Error), and calls ScoreForTaskException on every scorer instead of Score. The eval continues — no cases are skipped.By default, ScoreForTaskException returns a single score of 0.0. Override it on your IScorer to return a custom fallback score, return an empty list to omit scoring for that case, or re-throw to abort the eval.#skip-compile
exception.type, exception.message, and exception.stacktrace attributes, visible in any OTel-compatible backend connected to Braintrust.Scorer throws an exception during eval (C# SDK v0.2.2+)
Scorer throws an exception during eval (C# SDK v0.2.2+)
When a scorer’s Score spans are named
Score method throws, the exception is recorded on that scorer’s span (with ActivityStatusCode.Error and an OTel exception event) and ScoreForScorerException is called as a fallback. Other scorers continue running unaffected.By default, ScoreForScorerException returns a single score of 0.0. Override it to return a custom fallback, return an empty list to omit the score, or re-throw to abort the eval.#skip-compile
score:<scorer_name> (e.g. score:my_scorer), making individual scorer traces distinguishable in Braintrust and any connected OTel backend.Run without uploading results
Sometimes you want to run your evaluation locally without creating an experiment in Braintrust — while iterating on a new scorer, wiring up a new eval pipeline, or running in an environment without a Braintrust API key. Your tasks and scorers still run and print a summary to your terminal; results just aren’t uploaded.- TypeScript
- Python
Via the CLI:Or in code:
Next steps
- Interpret results from your experiments
- Compare experiments to measure improvements
- Test complex agents to connect custom code to the playground
- Write scorers to measure quality
- Evaluation best practices for reliable, high-signal evals