Re: [Numpy-discussion] Installing

2014-03-03 Thread Søren
Hi Sze You need Python 2.7.x 32-bit version installed. I experienced this once when I accidentally had the 64-bit version of Python installed. kind regards Søren ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org

Re: [Numpy-discussion] numpy array to C API

2013-03-21 Thread Søren
't seem to work. (Under "Further Reading and References") cheers Søren On 21/03/2013 09:41, Valentin Haenel wrote: > Dear Søren, > > if you are new to interfacing python/numpy with C/C++, you may want to > check out: > > http://scipy-lectures.github.com/advanced

Re: [Numpy-discussion] numpy array to C API

2013-03-21 Thread Søren
Thanks Robert, for making that clear. I got a deprecated warning the second I added #include and I got scared off too fast in my exploring phase. Cheers Søren On 20/03/2013 17:03, Robert Kern wrote: > On Wed, Mar 20, 2013 at 1:59 PM, Søren wrote: >> Greetings >> >> I

[Numpy-discussion] numpy array to C API

2013-03-20 Thread Søren
Array but I can see in the compiler warnings, it is deprecated and I don't wanna start from scratch on legacy facilities. Going forward, what is the intended way of doing this with neat code on both sides and with a minimum of mem copy gymnastics overhead? thanks in adva

Re: [Numpy-discussion] Trick for fast

2012-02-03 Thread Søren Gammelmark
What about this? A = einsum("i,ij->", mass, x ** 2) B = einsum("i,ij,ik->jk", mass, x, x) I = A * eye(3) - B /Søren On 3 February 2012 15:10, wrote: > On Fri, Feb 3, 2012 at 8:44 AM, Alan G Isaac wrote: > > On 2/3/2012 5:16 AM, santhu kumar wrote: > >

[Numpy-discussion] einsum evaluation order

2012-01-24 Thread Søren Gammelmark
nto existing numpy operations (e.g. tensordot). How to incorporate issues of storage layout etc, however, I have no idea. In any case I think it might be nice to write explicitly how the expression in einsum is evaluated in the docs. Søren Gammelmark PhD-student Department of Physics and Astronomy

Re: [Numpy-discussion] Installing numpy with MKL

2010-08-05 Thread Søren Gammelmark
It seems to me, that you are using an libiomp5 for Intel Itanium (lib/intel64) or such, but an MKL for EM64T-processors (lib/em64t). In my case I used EM64T in all cases (I'm running AMD Opteron) . I don't think the two types of libraries are compatible, but I might be wrong. /Søren

Re: [Numpy-discussion] Installing numpy with MKL

2010-08-03 Thread Søren Gammelmark
I'm not entirely sure I understand the link, but if it has anything to do with the compiler it seems to me that it should be the Intel compiler. The python I use is compiled with GCC but everything in numpy is done with the Intel compilers. Shouldn't it then be something w

Re: [Numpy-discussion] Installing numpy with MKL

2010-08-03 Thread Søren Gammelmark
ch or have you found a less invasive method since? Now on to SciPy... :-) Thankyou for your help Søren On 03-08-2010 18:33, Dag Sverre Seljebotn wrote: > Søren Gammelmark wrote: > >> Hi everyone >> >> I realize that this e-mail has been written a lot of times before. I

[Numpy-discussion] Installing numpy with MKL

2010-08-03 Thread Søren Gammelmark
ed with this sort of thing but I usually have few problems compiling a stand-alone Fortran or C/C++ program that uses MKL. I would greatly appreciate it if anyone could help with this. Regards Søren Gammelmark P.s: The operating system is Linux/CentOS 4.4, x86_64 Running from numpy source direc

Re: [Numpy-discussion] Weave Ext_tools converters not working??

2008-11-17 Thread Søren Nielsen
at 15:42 +0100, Søren Nielsen wrote: > why > test(x,y) = 2; > and not > test[x][y] = 2; > ? > > Nadav > > Can anyone explain why this fails? This piece of code runs perfectly using > weave.inline and type_converters = blitz.. >

[Numpy-discussion] Weave Ext_tools converters not working??

2008-11-17 Thread Søren Nielsen
Can anyone explain why this fails? This piece of code runs perfectly using weave.inline and type_converters = blitz.. Obviously it can't handle 2D arrays anymore. It's just a stupid example to illustrate that. Thanks, Soren CODE : -

Re: [Numpy-discussion] ANN: I wrote some Numpy + SWIG + MinGW simple examples

2008-11-14 Thread Søren Nielsen
Hi Egor, Thanks for a very nice tutorial! Have you tried doing manipulations with 2D arrays?? or do you know how to tackle it? Regards, Soren On Fri, Nov 14, 2008 at 12:32 AM, Egor Zindy <[EMAIL PROTECTED]> wrote: > Hello list! > > To get my head round the numpy.i interface for SWIG, I wrote so

[Numpy-discussion] indexing numpy arrays in extensions created with ext_tools

2008-10-31 Thread Søren Nielsen
Hi, I'm trying to make a weave python extension to use in my program. I already did it in inline, but that doesn't work with py2exe (needs compiler), so I'm creating extensions instead using ext_tools. Is there a way I can use blitz with ext_tools? so that I can refer to numpy arrays like a(x,y)

Re: [Numpy-discussion] Extending an ndarray

2008-05-14 Thread Søren Nielsen
upper left corner of a larger array of zeros > b=zeros((10,10)) > b[:5,:5]=a > > > On Wed, May 14, 2008 at 2:48 PM, Søren Nielsen > <[EMAIL PROTECTED]> wrote: > > Hi, > > > > I've loaded an image into a ndarray. I'd like to extend the ndarray wit

[Numpy-discussion] Extending an ndarray

2008-05-14 Thread Søren Nielsen
Hi, I've loaded an image into a ndarray. I'd like to extend the ndarray with a border of zeros all around the ndarray.. does anyone here know how to do this? Thanks, Soren ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scip

Re: [Numpy-discussion] numpy large arrays?

2007-12-13 Thread Søren Dyrsting
e data amounts in the task is too close to the ceiling of memory. The approach: "First make it work. Then optimize" apparently isn't suitable here. Thanks /Søren ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projec

[Numpy-discussion] numpy large arrays?

2007-12-12 Thread Søren Dyrsting
nce of Python/NumPy and should consider other environments. Fortran, C, BLAS, LAPACK e.t.c. - Am I misusing NumPy? Changing coding style will be a good workaround and even perform on larger datasets without errors? Thanks in advance /Søren ___ Numpy-discus