[fix] fix order bug Update arena_hard.py#2015
Merged
Conversation
There was a problem hiding this comment.
Copilot reviewed 1 out of 1 changed files in this pull request and generated no comments.
Comments suppressed due to low confidence (1)
opencompass/datasets/subjective/arena_hard.py:149
- Removing sorted() now returns keys in insertion order, which may differ from the previous behavior. Ensure that this change aligns with the intended order for win rate calculation.
names = list(elo_ratings.keys())
acylam
approved these changes
Apr 10, 2025
Collaborator
acylam
left a comment
acylam
left a comment
There was a problem hiding this comment.
Might be more robust to join scores to the stats dataframe on model_name, but this will do for now.
Collaborator
|
Agree with Junyao's comments, please consider join the scores to stats. @bittersweet1999 |
domonic18
pushed a commit
to domonic18/opencompass
that referenced
this pull request
Apr 14, 2025
* 'main' of https://github.com/domonic18/opencompass: [Feature] LLM Judge sanity check (open-compass#2012) [Fix] fix order bug Update arena_hard.py (open-compass#2015) [Fix] Fix compare error when k is list in base_evaluator (open-compass#2010)
stephen-nju
pushed a commit
to stephen-nju/opencompass
that referenced
this pull request
May 14, 2025
zyc140345
pushed a commit
to zyc140345/opencompass
that referenced
this pull request
Oct 23, 2025
iamkaia
pushed a commit
to iamkaia/opencompass
that referenced
this pull request
Feb 4, 2026
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.
Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
Please describe the motivation of this PR and the goal you want to achieve through this PR.
Modification
Please briefly describe what modification is made in this PR.
BC-breaking (Optional)
Does the modification introduce changes that break the backward compatibility of the downstream repositories?
If so, please describe how it breaks the compatibility and how the downstream projects should modify their code to keep compatibility with this PR.
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here and update the documentation.
Checklist
Before PR:
After PR: