Add eval_visualization_page optional field to ScoreEntry schema #526
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds
eval_visualization_pageas an optional string field to theScoreEntryschema forscores.jsonfiles.Changes
eval_visualization_page: Optional[str]field to theScoreEntryclass inscripts/validate_schema.pyNone) and described as "URL to the evaluation visualization page"Example usage
After this change, score entries can optionally include:
{ "benchmark": "swe-bench", "score": 74.2, "metric": "accuracy", "cost_per_instance": 1.19, "average_runtime": 534.0, "full_archive": "https://results.eval.all-hands.dev/...", "tags": ["swe-bench"], "agent_version": "v1.8.3", "submission_time": "2026-01-26T16:02:48.428351+00:00", "eval_visualization_page": "https://laminar.sh/shared/evals/..." }Validation
@neubig can click here to continue refining the PR