Hallo!
First, my plan is to add to numpy.i, typemaps for signatures like the
following:
%typemap(argout) (double** ARGOUT_ARRAY1, int* DIM1)
It is important to note that even though the same argument *names* are
used, this is a different typemap signature than
Matthew Perry wrote:
Hi all,
I'm not sure if my terminology is familiar but I'm trying to do a
moving window analysis (ie a spatial filter or kernel) on a 2-D
array representing elevation. For example, a 3x3 window centered on
each cell is used to calculate the derivate slope of that cell.
On Montag 26 November 2007, Matthew Perry wrote:
Hi all,
I'm not sure if my terminology is familiar but I'm trying to do a
moving window analysis (ie a spatial filter or kernel) on a 2-D
array representing elevation. For example, a 3x3 window centered on
each cell is used to calculate the
Hi Matthew
On Sun, Nov 25, 2007 at 05:00:48PM -0800, Matthew Perry wrote:
I'm not sure if my terminology is familiar but I'm trying to do a
moving window analysis (ie a spatial filter or kernel) on a 2-D
array representing elevation. For example, a 3x3 window centered on
each cell is used to
Is the numpy.typeNA dictionary out of date? All of the verbose names for
datatypes are captialized, and can't be found in the numpy namespace.
Thanks,
Darren
___
Numpy-discussion mailing list
Numpy-discussion@scipy.org
Dear all:
After using numpy for several weeks, I am very happy about it and
deeply impressed about the performance improvements it brings in my
python code. Now I have stumbled upon a problem, where I cannot use
numpy to eliminate all my loops in python.
Currently the return value of inner(a,
Bill Spotz wrote:
First, my plan is to add to numpy.i, typemaps for signatures like the
following:
%typemap(argout) (double** ARGOUT_ARRAY1, int* DIM1)
It is important to note that even though the same argument *names*
are used, this is a different typemap signature than
