Open cjnolet opened 6 months ago
Hi! I'm really interested in helping to implement this feature.
From what I understand, the request involves:
ivf-pq
and exposing public API.ivf-pq
to use the PQ API, eliminating duplicated code.ivf
that can be flexibly combined with SQ, PQ, BinaryQ and other quantization methods. (related to issues #106 and #139 )Is there a concrete plan for this yet? I noticed that some discussion has taken place in #211 ,but I didn't find a clear conclusion there. As mentioned in this comment and this one, the PQ API should at least cover training, encoding and searching. It seems like CuVS prefers a stateless style rather than holding trained quantizer in a index like FAISS does.
Looking forward to collaborating on this!
Hi Maintainers! I'm still very interested in contributing to this feature and would appreciate any feedback.
We need a separate product quantization API that is decoupled from IVF but can still be composed into IVF.
Ideally this API would follow FAISS or Scikit-learn'a transformer estimators.