Retrieval eval + benchmark harness (tooling)#558
Closed
tobocop2 wants to merge 1 commit into
Closed
Conversation
The blind noise-calibrated retrieval eval harness (evals/retrieval) and the preregistered lilbee-vs-baseline benchmark (evals/benchmark) with its Qwen3-0.6B results, split out of the core retrieval work so the harness tooling lives on its own branch instead of cluttering lilbee's core. Runs against a deployed lilbee; imports the public API only.
Owner
Author
|
Not merging the harness into main. It stays on its own standalone branch (evals/retrieval-harness) as separate tooling; closing this PR so it never targets main. Branch and history remain intact. |
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
1 participant
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.
The blind retrieval eval harness (
evals/retrieval) and the preregistered lilbee-vs-baseline benchmark (evals/benchmark), split out of the core retrieval work (#557) so the harness tooling lives on its own branch instead of cluttering lilbee's core.Runs against a deployed lilbee and imports the public API only, so nothing in
src/depends on it. Includes the Qwen3-0.6B benchmark results (evals/benchmark/RESULTS.md+ gzipped TREC run files) that validated the retrieval features in #557.