docs: correct strict_mode score direction for higher-is-better metrics - #183
Open
crubn wants to merge 1 commit into
Open
docs: correct strict_mode score direction for higher-is-better metrics#183crubn wants to merge 1 commit into
crubn wants to merge 1 commit into
Conversation
These metric pages describe strict_mode as "0 for perfection, 1 otherwise", but for higher-is-better metrics strict_mode sets the threshold to 1, so a perfect run scores 1 (not 0). Flips the wording to "1 for perfection, 0 otherwise" to match the code and deepeval's own metric docs. Inverted metrics (hallucination, bias, toxicity, etc.) are intentionally left unchanged. Co-Authored-By: Claude Opus 4.8 <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.
These metric pages describe strict_mode as "0 for perfection, 1 otherwise", but for higher-is-better metrics strict_mode sets the threshold to 1, so a perfect run scores 1 (not 0). Flips the wording to "1 for perfection, 0 otherwise" to match the code and deepeval's own metric docs. Inverted metrics (hallucination, bias, toxicity, etc.) are intentionally left unchanged.