You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
when using refinement API, we found that the distances (for same pair of vectors) are different between ground truth and refinement, resulting in refinement not always capturing the k closest neighbors from the candidates.
See below for an example of the ground truth in the range of candidates but refinement failing to pick that out. 41363 is one of the candidates, and should be ground truth, but not getting identified by refinement(the line of output under "indices" is the result of refine ), selecting 9 correct candidates except 41363
Describe the bug
when using refinement API, we found that the distances (for same pair of vectors) are different between ground truth and refinement, resulting in refinement not always capturing the k closest neighbors from the candidates.
See below for an example of the ground truth in the range of candidates but refinement failing to pick that out. 41363 is one of the candidates, and should be ground truth, but not getting identified by refinement(the line of output under "indices" is the result of refine ), selecting 9 correct candidates except 41363
Steps/Code to reproduce bug
Follow this guide http://matthewrocklin.com/blog/work/2018/02/28/minimal-bug-reports to craft a minimal bug report. This helps us reproduce the issue you're having and resolve the issue more quickly.
Expected behavior
Refine should be able to recognize the ground truth vector if it's in the candidates
Environment details (please complete the following information):
Additional context
Add any other context about the problem here.
The text was updated successfully, but these errors were encountered: