feat(evaluation): add trajectory improvement metrics - #9
Open
linhongyu510 wants to merge 2 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
Add trajectory-level improvement metrics to EdgeBench evaluation history so iterative agent runs can be analyzed beyond the final score.
Metrics include initial, final, and best values; total improvement; improving/non-improving counts; and time to first improvement and best result. Both maximize and minimize directions are supported.
Agent-visible history is recomputed from agent-visible entries, so automatic submissions are not leaked.
Robustness
submitted_atValidation
pytest tests/test_trajectory_metrics.py -q— 8 passedgit diff --checkAI assistance
Developed with AI assistance; metric semantics and visibility boundaries were manually reviewed.