Hmm, it seems my original message did not come through? Not in gmane, at
least... Well, here's again:
Hi numpy and/or gdal guru's,
I'm suddenly getting into trouble compiling gdal's python extension,
when it includes ndarrayobject.h from numpy. First it complains about my
python not being unicode
is there a method for numpy arrays and matrices to get/set a particular
column
i know that a row can be fetched by mymat[1,:] etc
can this be done for a column
dn
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mail
On 31/10/2007, Ray S <[EMAIL PROTECTED]> wrote:
> I am using
> fftRes = abs(fft.rfft(data_array[end-2**15:end]))
> to do running analysis on streaming data. The N never changes.
> It sucks memory up at ~1MB/sec with 70kHz data rate and 290 ffts/sec.
> (Interestingly, Numeric FFT accumulates much sl
Ray S wrote:
> I am using
> fftRes = abs(fft.rfft(data_array[end-2**15:end]))
> to do running analysis on streaming data. The N never changes.
> It sucks memory up at ~1MB/sec with 70kHz data rate and 290 ffts/sec.
> (Interestingly, Numeric FFT accumulates much slower..)
> (Commenting out that one
I am using
fftRes = abs(fft.rfft(data_array[end-2**15:end]))
to do running analysis on streaming data. The N never changes.
It sucks memory up at ~1MB/sec with 70kHz data rate and 290 ffts/sec.
(Interestingly, Numeric FFT accumulates much slower..)
(Commenting out that one line stops memory growth.
On Oct 31, 2007 3:18 AM, Francesc Altet <[EMAIL PROTECTED]> wrote:
[SNIP]
> Incidentally, all the improvements of the PyTables flavor of numexpr
> have been reported to the original authors, but, for the sake of
> keeping numexpr simple, they decided to implement only some of them.
> However, peo
Charles R Harris wrote:
> On 10/31/07, Robert Kern <[EMAIL PROTECTED]> wrote:
>> Charles R Harris wrote:
>>> On 10/31/07, Alan G Isaac <[EMAIL PROTECTED]> wrote:
>>> 1.0**numpy.array([1,2,3])
array([ 1., 1., 1.])
>>> 1.0**numpy.mat([1,2,3])
Traceback (most recent call last):
>>>
On 10/31/07, Robert Kern <[EMAIL PROTECTED]> wrote:
> Charles R Harris wrote:
> > On 10/31/07, Alan G Isaac <[EMAIL PROTECTED]> wrote:
> > 1.0**numpy.array([1,2,3])
> >> array([ 1., 1., 1.])
> > 1.0**numpy.mat([1,2,3])
> >> Traceback (most recent call last):
> >> File "", line 1, in
>
Charles R Harris wrote:
> On 10/31/07, Alan G Isaac <[EMAIL PROTECTED]> wrote:
> 1.0**numpy.array([1,2,3])
>> array([ 1., 1., 1.])
> 1.0**numpy.mat([1,2,3])
>> Traceback (most recent call last):
>> File "", line 1, in
>> TypeError: unsupported operand type(s) for ** or pow(): 'float' a
On Oct 30, 2007 11:40 PM, Alan G Isaac <[EMAIL PROTECTED]> wrote:
> >>> 1.0**numpy.array([1,2,3])
> array([ 1., 1., 1.])
> >>> 1.0**numpy.mat([1,2,3])
> Traceback (most recent call last):
> File "", line 1, in
> TypeError: unsupported operand type(s) for ** or pow(): 'float' and 'matrix'
>
> W
Btw forgot some info:
gentoo linux, amd64
numpy 1.0.3.1
gdal from svn, updated today
python 2.5.1
Cheers,
Vincent.
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
http://projects.scipy.org/mailman/listinfo/numpy-discussion
A Wednesday 31 October 2007, Mathew Yeates escrigué:
[...]
> I also took a look at NumExpr. While it wasn't something I needed for
> vectorizing, it still looks very interesting. What kinds of
> performance improvements would be expected using this?
Well, for some speedup figures you can always ch
12 matches
Mail list logo
