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
Is your feature request related to a problem? Please describe.
BIGANN is one of the popular vector search dataset to measure the performance. However, they follow different format for Base data, Query data and Ground truth. Currently, Vector Search Neighbor param doesn't support Ground truth format. This is different from base data, hence, BigANNVectorDataSet should extend support to read, parse, convert it into neighbors like hdf5 for "bin" extension.
Describe the solution you'd like
Extend BigANN Dataset to support new extension "bin" that can parse ground truth and can be used as input for neighbors data set .
Describe alternatives you've considered
Manually convert it into hdf5 or previously supported format like fbin/u8bin
Additional context
N/A
The text was updated successfully, but these errors were encountered:
This was previously supported only in perf-tool . It was not added in osb since recall was not supported. With recall support, adding this format, will help users to gradually move out of perf-tool and use OSB for all use cases.
Is your feature request related to a problem? Please describe.
BIGANN is one of the popular vector search dataset to measure the performance. However, they follow different format for Base data, Query data and Ground truth. Currently, Vector Search Neighbor param doesn't support Ground truth format. This is different from base data, hence, BigANNVectorDataSet should extend support to read, parse, convert it into neighbors like hdf5 for "bin" extension.
Describe the solution you'd like
Extend BigANN Dataset to support new extension "bin" that can parse ground truth and can be used as input for neighbors data set .
Describe alternatives you've considered
Manually convert it into hdf5 or previously supported format like fbin/u8bin
Additional context
N/A
The text was updated successfully, but these errors were encountered: