Re: [Numpy-discussion] ld.so.1 linker errors building numpy

Park Hays wrote: > I have been fighting for a couple weeks to get numpy installed, on the > way to a full scipy+matplotlib system. I tried installing numpy on a solaris machine on SPARC too, with the added difficulty to have only a local account on the machine (without a compiler: had to build m

Re: [Numpy-discussion] What is the different between nanmin and min ?

Timothy Hochberg wrote: > > On 7/18/07, *Robert Kern* <[EMAIL PROTECTED] > > wrote: > > Timothy Hochberg wrote: > > > The time is one issue. Another is that ignoring NaNs is only > correct if > > you are treating NaNs as missing values. If instead you ar

Re: [Numpy-discussion] What is the different between nanmin and min ?

On 7/18/07, Robert Kern <[EMAIL PROTECTED]> wrote: Timothy Hochberg wrote: > The time is one issue. Another is that ignoring NaNs is only correct if > you are treating NaNs as missing values. If instead you are treating > them as non numbers, the results of some bogus computation, then raising

[Numpy-discussion] Recarray to and from sqlite

Hi, I am trying to write a couple of simple functions to (1) save recarray's to an sqlite database and (2) load a recarray from an sqllite database. I am stuck on 2 points and hope there are some people on this list that use sqlite for numpy stuff. 1. How to detect the variable names and types fr

Re: [Numpy-discussion] convert csv file into recarray without pre-specifying dtypes and variable names

Hi Torgil, 1. I got an email from Tim about this issue: "I finally got around to doing some more quantitative comparisons between your code and the more complicated version that I proposed. The idea behind my code was to minimize memory usage -- I figured that keeping the memory usage low would m

Re: [Numpy-discussion] convert csv file into recarray without pre-specifying dtypes and variable names

Nice, I haven't gone through all details. That's a nice new "missing" feature, maybe all instances where we can't find a conversion should be "nan". A few comments: 1. The "load_search" functions contains all memory/performance overhead that we wanted to avoid with the fromiter function. Does thi

Re: [Numpy-discussion] Logical Selector

Xavier Gnata wrote: > Well maybe it is a bug on my box (thunderbird) but the topic of the > thread is "-lmkl_lapack64 on i368 ??". > Nothing to do with "Logical Selector" ;) > Should I post another mail about this topic? > > Xavier > ps : I'm just sorry for the noise if it is a bug on my side.

Re: [Numpy-discussion] Logical Selector

Eric Firing wrote: > Robert Kern wrote: > >> Geoffrey Zhu wrote: >> >>> Hi Everyone, >>> >>> I am finding that numpy cannot operate on boolean arrays. For example, >>> the following does not work: >>> >>> x=3Darray([(1,2),(2,1),(3,1),(4,1)]) >>> >>> x[x[:,0]>x[:,1] and x[1:]>1,:] >>> >>> It

Re: [Numpy-discussion] Logical Selector

Robert Kern wrote: > Geoffrey Zhu wrote: >> Hi Everyone, >> >> I am finding that numpy cannot operate on boolean arrays. For example, >> the following does not work: >> >> x=3Darray([(1,2),(2,1),(3,1),(4,1)]) >> >> x[x[:,0]>x[:,1] and x[1:]>1,:] >> >> It gives me an syntax error: >> >>

Re: [Numpy-discussion] Logical Selector

Geoffrey Zhu wrote: > Hi Everyone, > > I am finding that numpy cannot operate on boolean arrays. For example, > the following does not work: > > x=3Darray([(1,2),(2,1),(3,1),(4,1)]) > > x[x[:,0]>x[:,1] and x[1:]>1,:] > > It gives me an syntax error: > > --- > Traceback (most re

[Numpy-discussion] Logical Selector

Hi Everyone, I am finding that numpy cannot operate on boolean arrays. For example, the following does not work: x=3Darray([(1,2),(2,1),(3,1),(4,1)]) x[x[:,0]>x[:,1] and x[1:]>1,:] It gives me an syntax error: --- Traceback (most recent call last): File "", line 1, in x[

[Numpy-discussion] -lmkl_lapack64 on i368 ??

Hi, I'm trying to update numpy by compiling the up to date svn: I get this error : gcc: numpy/linalg/lapack_litemodule.c gcc -pthread -shared build/temp.linux-i686-2.4/numpy/linalg/lapack_litemodule.o -lmkl_lapack32 -lmkl_lapack64 -lmkl -lvml -lguide -lpthread -o build/lib.linux-i686-2.4/numpy

Re: [Numpy-discussion] What is the different between nanmin and min ?

Timothy Hochberg wrote: > The time is one issue. Another is that ignoring NaNs is only correct if > you are treating NaNs as missing values. If instead you are treating > them as non numbers, the results of some bogus computation, then raising > an error is a more appropriate response. If one was

[Numpy-discussion] ld.so.1 linker errors building numpy

I have been fighting for a couple weeks to get numpy installed, on the way to a full scipy+matplotlib system. At this point, the transcript looks something like: python Python 2.5 (r25:51908, Sep 20 2006, 06:18:53) [GCC 3.4.6] on sunos5 from numpy import * -- stack trace, cut out except for

Re: [Numpy-discussion] What is the different between nanmin and min ?

On 7/17/07, Timothy Hochberg <[EMAIL PROTECTED]> wrote: > The time is one issue. Another is that ignoring NaNs is only correct if you > are treating NaNs as missing values. If instead you are treating them as non > numbers, the results of some bogus computation, then raising an error is a > more ap