Repository navigation
Adopt Qntz 0.2.2 and bound reported IVF distances - #19
Merged
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
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.
Require Qntz 0.2.2 so IVF-RaBitQ consumers receive its signed edge correction. Keep signed estimates through candidate ranking, then floor negative final reported distances at zero in both compact and exact-reranking modes. Expand the self-query regression to cover 200 vectors in both modes.
Validation: registry-only Qntz 0.2.2 resolution with the published checksum; 17 IVF-RaBitQ tests pass, including save/load; all-feature library nextest 613 passed, 5 skipped; formatting and both canonical Clippy configurations pass. The local all-feature gates use Python 3.11 because the system Python 3.9 is below the existing ABI minimum.