cub::DeviceBatchedTopK users want to be able to specify the tie-breaking behavior in addition to requesting deterministic results.
Specifically, these are the options users want to be able to request.
require(...) |
which items are selected |
determinism::not_guaranteed |
non-deterministic among tied elements (fast path) |
determinism::run_to_run |
deterministic; implementation-defined tie-break |
determinism::run_to_run, tie_break::prefer_smaller_index |
deterministic; ties resolved toward smaller source index |
determinism::run_to_run, tie_break::prefer_larger_index |
deterministic; ties resolved toward larger source index |
This issue can be closed when there's a trie-breaking behavior option available for users to choose from when invoking cub::DeviceBatchedTopK
cub::DeviceBatchedTopKusers want to be able to specify the tie-breaking behavior in addition to requesting deterministic results.Specifically, these are the options users want to be able to request.
require(...)determinism::not_guaranteeddeterminism::run_to_rundeterminism::run_to_run, tie_break::prefer_smaller_indexdeterminism::run_to_run, tie_break::prefer_larger_indexThis issue can be closed when there's a trie-breaking behavior option available for users to choose from when invoking
cub::DeviceBatchedTopK