nce to share your
> opinions on IT & business topics through brief surveys -- and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______
> Numpy-discussion mailing list
> Numpy-discussion@lists.so
ays. For now, I've
always used arrays of floats (using gmticks values of dates).
Thanks you,
David
--
David Douard LOGILAB, Paris (France)
Formations Python, Zope, Plone, Debian : http://www.logilab.fr/formations
Développement logiciel sur mesure :
): why does uint_n arithmetics are done
in the Z/(2**n)Z field (not sure about the maths correctness here)? I mean:
>>> a = numpy.uint8(10)
>>> a*a
100
>>> a*a*a # I'd like to have 255 here
232
>>> 1000%256
232
It would be really a nice fe
, :]
Unless I'm wrong, one can simplify a (very) little bit this line:
d = A[:, newaxis, :] - B
> # written as 3 expressions for more clarity
> d = sqrt((d**2).sum(axis=2))
> return d
>
--
David Douard LOGILAB, Paris (France)
F
: diag(x[:,0])
Out[18]:
array([[ 0.2287158 , 0., 0.],
[ 0., 0.50571537, 0. ],
[ 0., 0., 0.72304857]])
What else would you like?
David
> Joris: The Numpy Example List looks good. I hadn't come across that be
4680' would be fine.
Maybe something like
>>> '%.13f'%(lam**2)
David
--
David Douard LOGILAB, Paris (France)
Formations Python, Zope, Plone, Debian : http://www.logilab.fr/formations
Développement logiciel sur mesure : http://www.log
;increase the number of
digits", not have the "optimal" number of digits (as long as this is
meaningfull).
But I may have missed something.
David
--
David Douard LOGILAB, Paris (France)
Formations Python, Zope, Plone, Debian : http://www.logilab.fr/formati
