Improve efficiency in factual correctness for precision mode #1578
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
dosubot
bot
added
the
size:S
shahules786
approved these changes
Oct 25, 2024
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.
Description
This pull request optimizes the
_single_turn_ascorefunction by conditionally skipping unnecessary computations when the mode is set to "precision." Previously, the function calculatedresponse_referenceregardless of the scoring mode, which consumed resources and potentially increased processing costs. By avoiding theresponse_referencecalculation in "precision" mode, this update aims to enhance speed and reduce computational expenses.Changes Made
_single_turn_ascorefunction:response_reference: Theresponse_referenceis now computed only when the mode is not "precision."