tzaeschke opened this issue 6 years ago · 1 comments
See TinSpin tests using v16
Resolved, this turned out to be a configuration problem in the TinSpin set-up that used Manhattan L1 distance instead of Euclidean distance for kNN queries.