Re: [Numpy-discussion] 64-bit windows numpy / scipy wheels for testing

2014-07-27 Thread Robert McGibbon
I forked Olivier's example project to use the same infrastructure for building conda binaries and deploying them to binstar, which might also be useful for some projects. https://github.com/rmcgibbo/python-appveyor-conda-example -Robert On Wed, Jul 9, 2014 at 3:53 PM, Robert McGibbon wrote: >

Re: [Numpy-discussion] numpy.mean still broken for largefloat32arrays

2014-07-27 Thread Sturla Molden
Nathaniel Smith wrote: > The problem here is that when summing up the values, the sum gets > large enough that after rounding, x + 1 = x and the sum stops > increasing. Interesting. That explains why the divide-and-conquer reduction is much more robust. Thanks :) Sturla _

Re: [Numpy-discussion] numpy.mean still broken for largefloat32arrays

2014-07-27 Thread RayS
Thanks for the clarification, but how is the numpy rounding directed? Round to nearest, ties to even? http://en.wikipedia.org/wiki/IEEE_floating_point#Rounding_rules Just curious, as I couldn't find a reference. - Ray At 07:44 AM 7/27/2014, you wrote: >On Sun, Jul 27, 2014 at 3:16 PM, RayS wro

Re: [Numpy-discussion] numpy.mean still broken for largefloat32arrays

2014-07-27 Thread Nathaniel Smith
On Sun, Jul 27, 2014 at 3:16 PM, RayS wrote: > At 02:04 AM 7/27/2014, you wrote: > >>You won't be able to do it by accident or omission or a lack of >>discipline. It's not a tempting public target like, say, np.seterr(). > > BTW, why not throw an overflow error in the large float32 sum() case? > I

Re: [Numpy-discussion] numpy.mean still broken for largefloat32arrays

2014-07-27 Thread RayS
At 02:04 AM 7/27/2014, you wrote: >You won't be able to do it by accident or omission or a lack of >discipline. It's not a tempting public target like, say, np.seterr(). BTW, why not throw an overflow error in the large float32 sum() case? Is it too expensive to check while accumulating? - Ray

Re: [Numpy-discussion] numpy.mean still broken for largefloat32arrays

2014-07-27 Thread Robert Kern
On Sun, Jul 27, 2014 at 9:56 AM, wrote: > > On Sun, Jul 27, 2014 at 4:24 AM, Robert Kern wrote: >> >> On Sun, Jul 27, 2014 at 7:04 AM, wrote: >> > >> > On Sat, Jul 26, 2014 at 5:19 PM, Sturla Molden >> > wrote: >> >> >> >> Robert Kern wrote: >> >> >> >> >> It would presumably require a globa

Re: [Numpy-discussion] numpy.mean still broken for largefloat32arrays

2014-07-27 Thread josef.pktd
On Sun, Jul 27, 2014 at 4:24 AM, Robert Kern wrote: > On Sun, Jul 27, 2014 at 7:04 AM, wrote: > > > > On Sat, Jul 26, 2014 at 5:19 PM, Sturla Molden > > wrote: > >> > >> Robert Kern wrote: > >> > >> >> It would presumably require a global threading.RLock for protecting > the > >> >> global st

Re: [Numpy-discussion] numpy.mean still broken for largefloat32arrays

2014-07-27 Thread Robert Kern
On Sun, Jul 27, 2014 at 7:04 AM, wrote: > > On Sat, Jul 26, 2014 at 5:19 PM, Sturla Molden > wrote: >> >> Robert Kern wrote: >> >> >> It would presumably require a global threading.RLock for protecting the >> >> global state. >> > >> > We would use thread-local storage like we currently do with