Package: gsl-bin
Version: 1.13+dfsg-1
Severity: normal
Hi Dirk,
Thanks for maintaining Debian's gsl-bin package.
Its "gsl-histogram" utility looks like it could be
a real time saver.
Unfortunately, it seems to me that I may have
stumbled upon a circumstance where it drops data.
Here's how to elicit the bug:
$ echo -e "1\n2\n3" | gsl-histogram 1 3 4
At least on my computer, the resulting output is
1 1.5 1
1.5 2 0
2 2.5 1
2.5 3 0
I'd like to draw your attention to the last line.
It says no data points are in the last bin, which
has a maximum value of 3.
However, you can see that
a.) "3" was passed as gsl-histogram's second
parameter, which the man page names "xmax",
and
b.) the original echo statement definitely
emitted a "3".
It seems to me that the data point equal to "3" is
dropped.
Perhaps gsl-histogram could be changed from
checking if data is
"less than"
xmax, to checking if data is
"less than or equal to"
xmax.
Thanks,
Kingsley
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (990, 'unstable'), (1, 'experimental')
Architecture: i386 (i686)
Kernel: Linux 2.6.25-2-686 (SMP w/2 CPU cores)
Locale: LANG=en_US, LC_CTYPE=en_US (charmap=ISO-8859-1)
Shell: /bin/sh linked to /bin/bash
Versions of packages gsl-bin depends on:
ii libc6 2.9-6 GNU C Library: Shared libraries
ii libgsl0ldbl 1.10-1 GNU Scientific Library (GSL) -- li
gsl-bin recommends no packages.
gsl-bin suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]