Chris wrote:
> There appears to be a bug in numpy's hypergeometric
> random number generator. Here is an example -- if I
> generate 1000 hg samples with 4 draws from a space
> with 30 successes and 10 failures:
>
> In [39]: x = hg(30, 10, 4, 1000)
>
> I should get a mean value of:
>
> In [40]:
On Sun, Dec 02, 2007 at 05:22:49PM -0800, Martin Spacek wrote:
> so I run python (with Andrew Straw's
> package VisionEgg) as a "realtime" priority process in windows on a dual
> core computer, which lets me reliably update the video frame buffer in
> time for the next refresh, without having to wo
There appears to be a bug in numpy's hypergeometric
random number generator. Here is an example -- if I
generate 1000 hg samples with 4 draws from a space
with 30 successes and 10 failures:
In [39]: x = hg(30, 10, 4, 1000)
I should get a mean value of:
In [40]: 4*30./40
Out[40]: 3.0
But the sa
Sebastian Haase wrote:
> reading this thread I have two comments.
> a) *Displaying* at 200Hz probably makes little sense, since humans
> would only see about max. of 30Hz (aka video frame rate).
> Consequently you would want to separate your data frame rate, that (as
> I understand) you want to sav
Hi,
I am a comaintainer of the python-scipy package in Debian and now it
seems to be in quite a good shape. However, the python-numpy package
is quite a mess, so as it usually goes in opensource, I got fedup and
I tried to clean it. But I noticed, that f2py was moved from external
package into num
