Hi Charles,
Thank you for your response!
I do think np.einsum() is really great. I am not clear about how that
ties to my question though, because I was thinking more in lines of
wrapping and reshaping the output (#1) and improve the documentation
(#2), where the proper outcome was already calcul
Take a look as einsum, it is quite good for such things.
Chuck
On Tue, Nov 25, 2014 at 9:06 PM, Yuxiang Wang wrote:
> Dear all,
>
> I have been doing tensor algebra recently (for continuum mechanics)
> and was looking into two common operations: tensor product & tensor
> contraction.
>
> 1. Ten
Dear all,
I have been doing tensor algebra recently (for continuum mechanics)
and was looking into two common operations: tensor product & tensor
contraction.
1. Tensor product
One common usage is:
a[i1, i2, i3, ..., iN, j1, j2, j3, ..., jM] = b[i1, i2, i3, ..., iN] *
c[j1, j2, j3, ..., jM]
I l
On Tue, Nov 25, 2014 at 11:50 PM, Andrea Gavana wrote:
>
> On 25 November 2014 at 19:33, David Cournapeau wrote:
>>
>>
>>
>> On Tue, Nov 25, 2014 at 6:10 PM, Sturla Molden
>> wrote:
>>>
>>> David Cournapeau wrote:
>>> > Shall we consider >> >
>>> > href="https://github.com/scipy/scipy/issues/41
On 25 November 2014 at 19:33, David Cournapeau wrote:
>
>
> On Tue, Nov 25, 2014 at 6:10 PM, Sturla Molden
> wrote:
>
>> David Cournapeau wrote:
>> > Shall we consider > > href="https://github.com/scipy/scipy/issues/4168";>
>> https://github.com/scipy/scipy/issues/4168
>> > to be a
>> > blocker
25.11.2014, 21:14, Nathaniel Smith kirjoitti:
[clip]
> (I guess scipy could create an overallocated copy and then take a
> slice at the right offset, but asking scipy to use such hacks to work
> around our bugs is clearly wrong.)
Note that the issue is not just with Scipy, but with *all* f2py code
On Tue, Nov 25, 2014 at 7:07 PM, Sturla Molden wrote:
> Nathaniel Smith wrote:
>> On Tue, Nov 25, 2014 at 12:53 PM, David Cournapeau
>> wrote:
>>> Shall we consider https://github.com/scipy/scipy/issues/4168 to be a blocker
>>> (the issue arises on scipy master as well as 0.14.1) ?
>>
>> Do you
On Tue, Nov 25, 2014 at 12:53 PM, David Cournapeau wrote:
> Shall we consider https://github.com/scipy/scipy/issues/4168 to be a blocker
> (the issue arises on scipy master as well as 0.14.1) ?
Do you think there's anything scipy can do about it? It looks like a
pure numpy bug to me.
-n
--
Nat
On Tue, Nov 25, 2014 at 6:10 PM, Sturla Molden
wrote:
> David Cournapeau wrote:
> > Shall we consider > href="https://github.com/scipy/scipy/issues/4168";>
> https://github.com/scipy/scipy/issues/4168
> > to be a
> > blocker (the issue arises on scipy master as well as 0.14.1) ?
> >
>
> It is r
David Cournapeau wrote:
> Shall we consider href="https://github.com/scipy/scipy/issues/4168";>https://github.com/scipy/scipy/issues/4168
> to be a
> blocker (the issue arises on scipy master as well as 0.14.1) ?
>
It is really bad, but does anyone know what is really going on?
Which changes t
Shall we consider https://github.com/scipy/scipy/issues/4168 to be a
blocker (the issue arises on scipy master as well as 0.14.1) ?
On Sun, Nov 23, 2014 at 11:13 PM, Pauli Virtanen wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Dear all,
>
> We have finally finished preparing the S
11 matches
Mail list logo
