be
reimplimented using an nd_grid instance.
Cheers,
David
--
**
David M. Kaplan
Charge de Recherche 1
Institut de Recherche pour le Developpement
Centre de Recherche Halieutique Mediterraneenne et Tropicale
av. Jean Monnet
B.P. 171
34203 Sete cedex
France
Phone
t; In [32]: a = range(100)
>
> In [33]: b = range(100)
>
> In [34]: %timeit [ x * y for x,y in zip(a,b) ]
> 1 loops, best of 3: 51.9 ?s per loop
>
> In [35]: %timeit [ i*j for i in a for j in b ]
> 100 loops, best of 3: 2.78 ms per loop
>
> Arnar
--
*
2008/6/16 ricardo soares <[EMAIL PROTECTED]>
> Get a $50 FREE Gift today and take advantage of our best limited time
> offer!
> After installing the software, simply register, make your first
> deposit of at least $10, and we will add $50 in hassle-free bonus
> chips to your player account.
>
> N
mediately making
conversion to an array unnecessary.
I leave it up to you which is best. I can add the line to convert to
array if desired.
Cheers,
David
> -Travis
>
--
**
David M. Kaplan
Charge de Recherche 1
Institut de Recherche pour le Developpement
Cen
t functionality that existed previously
except for one minor change - instead of returning a numpy array of
arrays, mgrid/ogrid now return a list of arrays. However, this is
unlikely to be a problem as the majority of users generally unpack the
results of mgrid/ogrid so that each matrix can be used in
desired. If not, I
recommend adding a ndgrid function to numpy that does the equivalent of
matlab [X,Y,Z,...] = ndgrid(x,y,z,...) and then making the current
meshgrid just call that changing the order of the first two arguments.
Cheers,
David
--
**********
David M
