fix default rescoring param choice for quantization rescoring#7570
Merged
fix default rescoring param choice for quantization rescoring#7570
Conversation
This comment was marked as resolved.
This comment was marked as resolved.
Sorry, something went wrong.
IvanPleshkov
approved these changes
Nov 20, 2025
timvisee
approved these changes
Nov 20, 2025
timvisee
pushed a commit
that referenced
this pull request
Nov 25, 2025
Merged
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
3 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.
This was causing inconsistent scoring between mutable and immutable segments.
Temporary workaround: use
rescoreparameter explicitly.