Repository navigation
Restore Muse Spark 1.3 text benchmark scores - #63
Merged
Merged
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.
Three provider failures left Muse Spark 1.3 without an overall text score at either effort. Resume the existing runs to recover those three pairs: both runs now have 600/600 scored pairs, while all 1,197 previously scored responses are unchanged.
Replace the two result files, remove their accepted-failure IDs from the release policy, update the documented gap count, and regenerate the web summary plus eight affected text charts and their manifest. Only Muse Spark 1.3 text results and dependent totals change. Dataset, prompts, inference settings, scoring rules, and the original six task results are unchanged.
Validation: 336 tests passed; Ruff check/format, benchmark validation, and summary/chart freshness passed. Benchmark validation retains 266 existing warnings for unrelated models. Verified the generated scores in the companion Playground local preview.
The prepared cv-model-playground snapshot update should merge after this PR.