Keith Goodman wrote:
>I prfr shrtr nams lke inv eig and sin.
>
>
Dwn wth vwls!! Srsly thgh:
>>> from numpy import linalg
>>> help(linalg.inv)
Help on function inv in module numpy.linalg.linalg:
inv(a)
>>> ???
While I prefer inverse to inv, I don't really care as long as the word
"inverse
On 7/16/06, Rick White <[EMAIL PROTECTED]> wrote:
> On Jul 16, 2006, at 11:47 AM, Alan G Isaac wrote:
>
> > On Sun, 16 Jul 2006, "David M. Cooke" apparently wrote:
> >> 'inverse' is not much longer than 'inv', and is more descriptive
> >
> > But 'inv' is quite universal (can you name a matrix langu
On Jul 16, 2006, at 11:47 AM, Alan G Isaac wrote:
> On Sun, 16 Jul 2006, "David M. Cooke" apparently wrote:
>> 'inverse' is not much longer than 'inv', and is more descriptive
>
> But 'inv' is quite universal (can you name a matrix language
> that uses 'inverse' instead?) and I think unambiguous (
On Sun, 16 Jul 2006, Charles R Harris apparently wrote:
> What is needed in the end is a good index with lots of
> crossreferences. Name choices are just choices
I mostly agree with this (although I think Matlab made some
bad choices in naming). As a point of reference for
a useful index see
On Sun, 16 Jul 2006, "David M. Cooke" apparently wrote:
> 'inverse' is not much longer than 'inv', and is more descriptive
But 'inv' is quite universal (can you name a matrix language
that uses 'inverse' instead?) and I think unambiguous (what
might it be confused with?).
Cheers,
Alan Isaac
On 7/15/06, Travis Oliphant <[EMAIL PROTECTED]> wrote:
Victoria G. Laidler wrote:> Jonathan Taylor wrote:>
It's not that we're concerned with MATLAB compatibility. But, franklyI've never heard that the short names MATLAB uses for some very commonoperations are a liability. So, when a common ope
On Jul 16, 2006, at 00:21 , Travis Oliphant wrote:
> Victoria G. Laidler wrote:
>> Jonathan Taylor wrote:
>>
>>> pseudoinverse
>>>
>>> it's the same name matlab uses:
>>>
>>> http://www.mathworks.com/access/helpdesk/help/techdoc/ref/pinv.html
>>>
>>
>> Thanks for the explanation.
>>
>> I'm puzzled
Victoria G. Laidler wrote:
> Jonathan Taylor wrote:
>
>
>> pseudoinverse
>>
>> it's the same name matlab uses:
>>
>> http://www.mathworks.com/access/helpdesk/help/techdoc/ref/pinv.html
>>
>
> Thanks for the explanation.
>
> I'm puzzled by the naming choice, however. Standard best practice i
Victoria G. Laidler wrote:
> Sven Schreiber wrote:
>
>
>> Jon Peirce schrieb:
>>
>>
>>
>>> There used to be a function generalized_inverse in the numpy.linalg
>>> module (certainly in 0.9.2).
>>>
>>> In numpy0.9.8 it seems to have been moved to the numpy.linalg.old
>>> subpackage. Does
Jon Peirce wrote:
> There used to be a function generalized_inverse in the numpy.linalg
> module (certainly in 0.9.2).
>
> In numpy0.9.8 it seems to have been moved to the numpy.linalg.old
> subpackage. Does that mean it's being dropped?
No. We are just emphasizing the new names. The old names
Victoria G. Laidler schrieb:
>
> I understand that for interactive use, short names are more convenient;
> but shouldn't they be available aliases to the more general names? Since
> numpy is primarily a software library, I wouldn't expect it to sacrifice
> a standard best-practice in order to
Jonathan Taylor wrote:
> pseudoinverse
>
> it's the same name matlab uses:
>
> http://www.mathworks.com/access/helpdesk/help/techdoc/ref/pinv.html
Thanks for the explanation.
I'm puzzled by the naming choice, however. Standard best practice in
writing software is to give understandable names, t
pseudoinverse
it's the same name matlab uses:
http://www.mathworks.com/access/helpdesk/help/techdoc/ref/pinv.html
Victoria G. Laidler wrote:
>Sven Schreiber wrote:
>
>
>
>>Jon Peirce schrieb:
>>
>>
>>
>>
>>>There used to be a function generalized_inverse in the numpy.linalg
>>>module (c
Sven Schreiber wrote:
>Jon Peirce schrieb:
>
>
>>There used to be a function generalized_inverse in the numpy.linalg
>>module (certainly in 0.9.2).
>>
>>In numpy0.9.8 it seems to have been moved to the numpy.linalg.old
>>subpackage. Does that mean it's being dropped? Did it have to move? Now
Jon Peirce schrieb:
> There used to be a function generalized_inverse in the numpy.linalg
> module (certainly in 0.9.2).
>
> In numpy0.9.8 it seems to have been moved to the numpy.linalg.old
> subpackage. Does that mean it's being dropped? Did it have to move? Now
> i have to add code to my pac
15 matches
Mail list logo
