On Fri, Jul 19, 2013 at 12:10 PM, Sebastian Berg
wrote:
> On Fri, 2013-07-19 at 16:14 +0100, Nathaniel Smith wrote:
>> On Thu, Jul 18, 2013 at 2:23 PM, Sebastian Berg
>> wrote:
>> > On Thu, 2013-07-18 at 13:52 +0100, Nathaniel Smith wrote:
>> >> Hi all,
>> >>
>
>>
>> What I mean is: Suppose we w
On 7/19/13, Yaroslav Halchenko wrote:
> I have just added a few more benchmarks, and here they come
> http://www.onerussian.com/tmp/numpy-vbench/vb_vb_linalg.html#numpy-linalg-pinv-a-float32
> it seems to be very recent so my only check based on 10 commits
> didn't pick it up yet so they are not p
I have just added a few more benchmarks, and here they come
http://www.onerussian.com/tmp/numpy-vbench/vb_vb_linalg.html#numpy-linalg-pinv-a-float32
it seems to be very recent so my only check based on 10 commits
didn't pick it up yet so they are not present in the summary table.
could well be rel
URL:
https://github.com/gbb/numpy-simple-select
> I've just released version 2.0 of simple select. In brief this is a drop-in
> replacement for numpy.select with the following qualities:
>
> - Faster! (benchmarks 2-5x faster than numpy.select depending on use case and
> faster than v1.0 sim
Hi all,
I've just released version 2.0 of simple select. In brief this is a drop-in
replacement for numpy.select with the following qualities:
- Faster! (benchmarks 2-5x faster than numpy.select depending on use case and
faster than v1.0 simpleselect)
- Full broadcasting.
- All bugs in numpy.s
On Thu, 18 Jul 2013, Charles R Harris wrote:
> yeah... That is how I thought "it is working", but I guess it was left
> without asanyarraying for additional flexibility/performance so any
> array-like object could be used, not just ndarray derived classes.
>Speaking of which,
On Thu, Jul 18, 2013 at 2:23 PM, Sebastian Berg
wrote:
> On Thu, 2013-07-18 at 13:52 +0100, Nathaniel Smith wrote:
>> Hi all,
>>
>
>>
>> So:
>>
>> QUESTION 1: does that sound right: that in a perfect world, the
>> current gufunc convention would be the only one, and that's what we
>> should work
Thanks Rob,
I agree. Your suggestion is the better way.
Colin W.
On 19/07/2013 11:09 AM, numpy-discussion-requ...@scipy.org wrote:
1. Today's Topics: 1. Re: User Guide (Rob Clewley)
[snip]
Message: 1
D
On Fri, 2013-07-19 at 16:14 +0100, Nathaniel Smith wrote:
> On Thu, Jul 18, 2013 at 2:23 PM, Sebastian Berg
> wrote:
> > On Thu, 2013-07-18 at 13:52 +0100, Nathaniel Smith wrote:
> >> Hi all,
> >>
>
> What I mean is: Suppose we wrote a gufunc for 'sum', where the
> intrinsic operation took a vec
On Fri, 2013-07-19 at 16:31 +0100, Nathaniel Smith wrote:
> On Thu, Jul 18, 2013 at 2:23 PM, Sebastian Berg
> wrote:
> > It is so difficult because of the fact that dot is basically a
> > combination of many functions:
> > o vector * vector -> vector
> > o vector * matrix -> matrix (add dimens
On Fri, Jul 19, 2013 at 5:31 PM, Nathaniel Smith wrote:
> 3) Extend the gufunc machinery to understand the idea that some core
> dimensions are allowed to take on a special "nonexistent" size. So the
> signature for dot would be:
> (m*,k) x (k, n*) -> (m*, n*)
> where '*' denotes dimensions who
On Thu, Jul 18, 2013 at 2:23 PM, Sebastian Berg
wrote:
> It is so difficult because of the fact that dot is basically a
> combination of many functions:
> o vector * vector -> vector
> o vector * matrix -> matrix (add dimensions to vector on right)
> o matrix * vector -> matrix (add dimensio
On Thu, Jul 18, 2013 at 2:52 PM, Nathaniel Smith wrote:
> Compare:
> gu_dot_leftwards(ones((10, 11, 4)), ones((11, 12, 3, 4))) -> (10, 12, 3, 4)
> versus
> gu_dot_rightwards(ones((4, 10, 11)), ones((3, 4, 11, 12))) -> (3, 4, 10, 12)
The second makes quite a bit more sense to me, and fits with
On Fri, Jul 19, 2013 at 12:21 AM, Rob Clewley wrote:
> "The exception: one can have arrays of python objects, including numpy
> objects, which allows arrays to contain different sized elements."
What are numpy objects? "numpy objects" -> "numpy ndarrays" or "numpy
ndarray objects"?
Stéfan
_
14 matches
Mail list logo
