[BUG] select-top-k returning different results for RADIX_8_BITS and RADIX_11_BITS implementations for larger k
Open
@achirkin is already working on this.
Since May 18, 2022.
bug
inactive-30d
inactive-90d
- Dominant language
- Cuda
- Stars
- 1k
- Forks
- 251
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 31
Description
Perhaps, somehow related to the undeterminism coming from the radix select-k implementation, this test case fails on some machines
https://github.com/rapidsai/raft/blob/25db984ad4bf9bc47e81d5507f7b91dfbfc8aefc/cpp/test/spatial/selection.cu#L457-L469
The weird detail here is that checking the in_dists with the two returned indices yields rather different values, even though the out_dists check passes.
Contributor guide
No contributing guide indexed for this repository
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.
Assessment
This issue has not been assessed yet.