-
Notifications
You must be signed in to change notification settings - Fork 6
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
Error ngt_remove_index() only with normalized distance types #17
Comments
Thanks for the detailed report, I am indeed able to reproduce the errors you see. |
Ok I made a reproducer using ngt-py and made a corresponding issue there ☝🏼 |
@cjrh @lerouxrgd this looks to be fixed in the latest release https://github.com/yahoojapan/NGT/releases/tag/v2.1.5 |
GitHub automatically closed this issue when I merged the PR, however there seems to be an issue remaining for Lorenz and SparseJaccard distances. I have mentioned it in the related NGT issue. |
As |
Summary
I've come across a problem when calling
index.remove(id: VecId)
, but it only happens with certain distance types:NormalizedAngle
NormalizedCosine
NormalizedL2
The common theme seems to be that these are normalized?
This is the error that is produced:
Reproducer
I've made a basic project with test cases:
ngtbug.zip
These are the versions in use:
and in the lock file,
ngt-sys
is at 2.1.3.This is test case, to explain what is happening:
This is the output from the test run:
The failures in
SparseJaccard
andLorentz
are interesting but unrelated to my issue. I need to useNormalizedCosine
for my application.Comments
It is possible this is an issue with the upstream NGT library. I am not sure but I decided to ask here first. It is also possible that I have missed some detail about these distance types are supposed to be used.
The text was updated successfully, but these errors were encountered: