-
Notifications
You must be signed in to change notification settings - Fork 449
cub::DeviceHistogram::HistogramEven: Incorrect result when LevelT
does not exactly match SampleT
#479
Comments
We should either fix this behavior in the backend or require that |
LevelT
does not exactly match SampleT
Let's update the API to remove the deduced |
That is an idea that have consequences, for example: when you histogram |
That's a good point, since the upper bound is exclusive. We'll find a different fix. |
Passing into
cub::DeviceHistogram::HistogramEven
bounds of type different from type of samples leads to wrong histogramming. Example constructed from the library code is below. If you change type oflower_level
andupper_level
tofloat
, all is OK, butint
as in the example produces wrong histogram [1, 0, 0, 0, 4, 0]. Applicable to 1.16.The text was updated successfully, but these errors were encountered: