[BUG] `cuvs-bench` recipe doesn't have a dependency on cuvs Python, but `create_groundtruth` requires it.
Open
Nobody has claimed this yet.
bug
- Dominant language
- Cuda
- Stars
- 854
- Forks
- 236
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 62
Description
I think we could get around 2 issues here:
- The cuvs-bench-cpu cannot use the gpu to generate ground truth
- The cuvs-bench doesn't have a hard dependnecy on cuvs python, even though it assumes it's installed to create_groundtruth.
We should test if cuvs is installed in the python environment, and if not, issue a warning that the ground truth could be much faster if cuvs were installed. Then we should fall back to numpy.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the cuvs-bench recipe and the create_groundtruth entry point mentioned in the issue. Check how the Python environment and GPU ground-truth generation are handled, then verify both benchmark variants. Done means cuvs is detected when available, a warning explains the slower path when it is absent, and numpy provides the fallback.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- numpy, python
- Domain
- machine-learning, tooling
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100