Re-add Weave Router (v0.54) and refresh Azure-Model-Router metrics - #44
Merged
Conversation
Syncs with RouterArena main after the no-training-policy retrain and the PR #98/#107 Azure re-evaluation. - Weave Router: re-added at rank 2 (RouterArena PR #109). v0.54 "clean retrain" — 6-model cluster routing trained only on OpenRouterBench labels + Artificial Analysis quality priors, no RouterArena prompts. Arena 72.82, Acc 76.32, Cost $0.94, Robustness 100.00; optimality metrics are blank (submission has no for_optimality entries). - Azure-Model-Router: refreshed to Arena 71.87, Acc 72.82, Cost $0.22, Robustness 71.43; optimality cleared to match README. Weave per-domain category_scores fall back to synthetic (no v0.54 prediction file imported); the stale flip_labels_weave-router.json is left in place. Metadata (model pool, description, links) updated to v0.54. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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.
Syncs with RouterArena main after the no-training-policy retrain and the PR #98/#107 Azure re-evaluation.
Weave per-domain category_scores fall back to synthetic (no v0.54 prediction file imported); the stale flip_labels_weave-router.json is left in place. Metadata (model pool, description, links) updated to v0.54.