Closed bixiou closed 10 months ago
I can confirm this was a change introduced in Hmisc 5.1.0, resulting from Hmisc:::describe.vector
's call to spikecomp
:
spikecomp(c(0, -0.1, 1), tresult = 'roundeddata')$x
I don't know the intended behaviour for spikecomp
, so have no suggestions on a fix. You could try 5.0.1 (archived) or 5.1.1 (not on CRAN).
Ok. It is a bug I can live with for now, especially if the bug is corrected in the next CRAN release.
Okay, I understand what's happening. spikecomp
is used to group (bin) "close enough" values together. This example is a little clearer:
describe(10^-seq(5))
It looks like 5.1-1 already has a fix, so I will close.
Running
describe(c(0, -0.1, 1))
returnsIt makes no sense that
0
because-0.001
in the output. This flawed behavior seems to occur as soon as there are some floats (decimal numbers).It is the first time I notice this bug. I use Hmisc version 5.1.0, R version 4.3.1 and RStudio version 2023.08.0-daily+53.