Added bucketization feature to IndexLSH. #4048
Open
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.
I have improved the sa_encode method within the IndexLSH class to enhance its functionality. With this modification, users are now able to clearly determine which hash bucket the index data has been assigned to. Specifically, after the sa_encode method processes the input data and computes the hash values, the method now stores the resulting hash bucket mappings in a 2D vector, providing a clear association between each data point and its corresponding hash bucket. This makes it easier for users to track and manage the distribution of index data across hash buckets during the Locality-Sensitive Hashing (LSH) process.