-
Notifications
You must be signed in to change notification settings - Fork 194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
can't find the right one using falconn v 1.3.1 #90
Comments
Internally, find_k_nearest_neighbors relies on the methods for finding candidates. So in principle what you described shouldn't happen. Just to clarify: what distance function are you using when you find the nearest neighbor yourself among the candidates returned by get_unique_candidates? |
I use Euclidean distance,for two normalized vector v1 v2,||v1-v2|| is calculated . |
FALCONN can certainly miss the nearest neighbor. But if the nearest neighbor appears in the candidate set, FALCONN should find it. What distance function are you using when you set up the FALCONN data structure? |
I used parameter as follows: |
I built a hash table with about 20,000 data, feature dimension is 256, but when using find_k_nearest_neighbors ,it can't find the right one;
and when using [get_unique_candidates] , it may return 2000~4000 candidates, including the right one ;
still i search all the data one by one ,
the final result is same as get_unique_candidates.
For example
When using find_k_nearest_neighbors (in our case k =9) can not find the shortest distance FuMingming, and may return 9 candidates with distance 0.66~0.7; so the right one is missed;
while using get_unique_candidates or get_duplicate_candidates it can find the right one ;
The text was updated successfully, but these errors were encountered: