Default threshold to zero #75
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
…related tests accordingly
elisno
requested review from
jwmueller and
ulya-tkch
and removed request for
jwmueller
ulya-tkch
reviewed
Apr 16, 2025
Co-authored-by: Ulyana <ulya.tkach@gmail.com>
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.
Key Info
What changed?
Default thresholds for arbitrary evals runs by TrustworthyRAG are now set to 0.
It means an eval other than trustworthiness and response_helpfulness (at the time of this writing) will not influence the value of
is_bad_responsewhen runningValidator.validate(). A user must provide their own threshold for their user-defined evals.