Expose match_score to benchmark compute_results#3915
Merged
samuelgarcia merged 3 commits intoJun 12, 2025
Conversation
samuelgarcia
reviewed
Jun 2, 2025
Member
|
Ciao @alejoe91. I would be more explicit and put the variable in the signature. |
…fix-match-score-in-benchmark
samuelgarcia
approved these changes
Jun 12, 2025
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
2 participants
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.
By default, match_score is 0.5, which means that all performance metrics for units with agreement below that are 0. This PR at least exposes the option to pass match_score