[Numpy-discussion] Re: Bytes Object and Metadata
faltet at carabos.com
Mon Mar 28 08:52:18 EST 2005
A Dilluns 28 Març 2005 17:13, Francesc Altet va escriure:
> Based on suggestions from Todd Miller on how
> to do this as efficiently as possible, I have arrived to the
> conclusions that the next conversions are the most efficient ones:
> In :na = numarray.arange(100*1000,shape=(100,1000))
> In :num = Numeric.arange(100*1000);num=num.resize((100,1000))
> In :t1=time();num2=Numeric.fromstring(na._data,
Er, sorry, there is in fact a more efficient way to convert from a
Numeric object to a numarray object that doesn't require any data copy
at all. This is:
In :num=Numeric.arange(100*1000, typecode="i");num=num.resize((100,1000))
Out:array([0, 1, 2, 3, 4],'i')
Out:0.0001010894775390625 # takes just 100 us!
In :na2[0,4] = 1 # modify a cell
Out:array([0, 1, 2, 3, 1],'i')
Out:array([0, 1, 2, 3, 1]) # na2 has been modified as well, so the
# data area is shared between num and na2
in fact, its speed is independent of the array size (as it should be
for a non-data-copying procedure):
# Create a Numeric object 10x larger
Out:0.00010204315185546875 # 100 us again!
This is because numarray has chosen to use a buffer object internally,
and that the Numeric object can be wrapped by a buffer object without
any actual data copy.
That drives me to think that, if the bytes object (that seems to be
implemented by Numeric3) could wrap the buffer object where numarray
objects hold its data, the conversion between Numeric3 <--> numarray
(or, in general, between those packages that deal with bytes objects
and other packages that deal with buffer objects) can be done with a
cost of 1 (that is, independent of the data size).
If this cannot be done (I mean, to get a safe bytes object from a
buffer object and vice-versa), well, it should be a pity. Do you think
that would be possible at all?
>qo< Francesc Altet http://www.carabos.com/
V V Cárabos Coop. V. Enjoy Data
More information about the NumPy-Discussion