Improve SimpleQA eval observability with structured logging and latency metadata#1790
Open
SeanHe727 wants to merge 1 commit into
Open
Improve SimpleQA eval observability with structured logging and latency metadata#1790SeanHe727 wants to merge 1 commit into
SeanHe727 wants to merge 1 commit into
Conversation
Author
|
Thanks for reviewing! This PR is intended as a small, backward-compatible improvement to make SimpleQA eval runs easier to reproduce and compare. It adds structured JSON logging, per-query latency tracking, and run metadata without changing the default eval behavior. Happy to adjust the output format or scope based on maintainer preferences. |
863ce4b to
d45c2c7
Compare
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
This PR improves the SimpleQA evaluation pipeline by adding structured logging, per-query latency tracking, and reproducibility metadata.
Changes
time.perf_counter()SMART_LLM_MODELusage toSMART_LLMnext()failuresMotivation
The previous eval output was primarily console-based, which made it harder to compare runs, track latency regressions, and reproduce evaluation results across model and configuration changes.
Compatibility
Existing eval behavior is preserved unless structured logging is enabled.
Testing