On Wed, May 18, 2011 at 8:57 AM, Mark Wiebe wrote:
> On Tue, May 17, 2011 at 8:53 PM, Charles R Harris <
> charlesr.har...@gmail.com> wrote:
>
>> On Tue, May 17, 2011 at 7:46 PM, Wieland Brendel
>> wrote:
>>
>>> > The equality being that the expression should be ~0?
>>>
>>> Exactly.
>>>
>>> > I
On Tue, May 17, 2011 at 8:53 PM, Charles R Harris wrote:
> On Tue, May 17, 2011 at 7:46 PM, Wieland Brendel
> wrote:
>
>> > The equality being that the expression should be ~0?
>>
>> Exactly.
>>
>> > I see the problem when the last index is in the range 235 - 390.
>>
>> Good to see I am not the
Thanks for your reply! I managed to open a ticket,
http://projects.scipy.org/numpy/ticket/1834
You are actually right, you can also just use zeros instead of random.
Maybe I can test a bit more tomorrow... but its 4am in the morning now ;-).
Thanks for your help and kindness!
Wieland
On Tue, May 17, 2011 at 8:09 PM, Wieland Brendel wrote:
> It also fails for
>
> T = random.random((2,d,d))
> W = random.random((2,d,d,i))
>
> and d > 2. For d = 3 it fails for i = 911...1365.
>
> Should I submit this as a bug (if so, how do I do that?) and/or contact the
> author Mark Wiebe?
>
>
It also fails for
T = random.random((2,d,d))
W = random.random((2,d,d,i))
and d > 2. For d = 3 it fails for i = 911...1365.
Should I submit this as a bug (if so, how do I do that?) and/or
contact the author Mark Wiebe?
Wieland
PS: How
On Tue, May 17, 2011 at 7:46 PM, Wieland Brendel wrote:
> > The equality being that the expression should be ~0?
>
> Exactly.
>
> > I see the problem when the last index is in the range 235 - 390.
>
> Good to see I am not the only one - I was getting crazy. Same range for me by
> the way.**> Out
On Tue, May 17, 2011 at 7:32 PM, Charles R Harris wrote:
>
>
> On Tue, May 17, 2011 at 6:47 PM, Wieland Brendel
> wrote:
>
>>
>> Hello,
>> I am encountering a very strange behaviour of einsum on my machine. I
>> tracked the problem down to the following test code:
>>
>> from numpy import *
>>
>>
> The equality being that the _expression_ should be ~0?
Exactly.
> I see the problem when the last index is in the range 235 - 390.
Good to see I am not the only one - I was getting crazy. Same range for me by the way.
> Out of curiosity, which machine/OS are you using? I'm
> The equality being that the _expression_ should be ~0?
Exactly.
> I see the problem when the last index is in the range 235 - 390.
Good to see I am not the only one - I was getting crazy. Same range for me by the way.
> Out of curiosity, which machine/OS are you using? I'm on 64 b
On Tue, May 17, 2011 at 6:47 PM, Wieland Brendel wrote:
>
> Hello,
> I am encountering a very strange behaviour of einsum on my machine. I
> tracked the problem down to the following test code:
>
> from numpy import *
>
> T = random.random((3,10,10))
> W = random.random((3,10,7,275))
>
> print all
Hello,
I am encountering a very strange behaviour of einsum on my machine. I
tracked the problem down to the following test code:
from numpy import *
T = random.random((3,10,10))
W = random.random((3,10,7,275))
print all(einsum('ij...,j...->i...',T[0],W[0]) +
einsum('ij...,j...->i...',T[1],W[1
11 matches
Mail list logo
