[Numpy-discussion] How to remove pages from the wiki ?

All, How can I remove pages from the wiki ? I ran into some that are clearly unrelated to numpy, scipy or programming... Thanks a lot in advance, P ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/n

Re: [Numpy-discussion] Academic citation ?

David, Thanks, but that's only part of what I need. I could also refer to Travis O's paper in Computing in Science and Engineering, but I wondered whether there wasn't something more up-to-date. So, other answers are still welcome. P. On Jan 25, 2009, at 8:17 PM, David Warde-Farley wrote: >

Re: [Numpy-discussion] Academic citation ?

I believe this is what you're looking for: http://www.scipy.org/Citing_SciPy On 25-Jan-09, at 6:45 PM, Pierre GM wrote: > All, > What is the most up-to-date way to cite Numpy and Scipy in an academic > journal ? > Thanks a lot in advance > P. > __

[Numpy-discussion] Academic citation ?

All, What is the most up-to-date way to cite Numpy and Scipy in an academic journal ? Thanks a lot in advance P. ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] glibc error

Sun, 25 Jan 2009 10:44:15 -0500, Gideon Simpson wrote: > Rebuilding the library against ATLAS 3.8.2 with lapack 3.1.1 seems to > have done the trick. I do get one failure: > > == > FAIL: test_umath.TestComplexFunctions.test_agai

Re: [Numpy-discussion] Having trouble installing Numpy on OS X

I ended by giving up and grabbing the binary. I'll get 2.5 for Numpy too. I did grab Xcode 2.5, which has gcc 4.0.1. I didn't feel up to manually doing a complete change to the latest gcc, at least while my needs are being met. Thanks, Nat On Jan 24, 2009, at 9:04 PM, Michael Abshoff wrot

Re: [Numpy-discussion] glibc error

Rebuilding the library against ATLAS 3.8.2 with lapack 3.1.1 seems to have done the trick. I do get one failure: == FAIL: test_umath.TestComplexFunctions.test_against_cmath --

Re: [Numpy-discussion] Suggested change for NaN, Infs float->int conversion

On Sun, Jan 25, 2009 at 4:35 AM, Matthew Brett wrote: > Hi, > > When converting arrays from float to ints, I notice that NaNs, Infs, > and -Infs all get the minimum integer value: > flts = np.array([np.nan, np.inf, -np.inf]) flts.astype(np.int16) > array([-32768, -32768, -32768], dtype=i

Re: [Numpy-discussion] Suggested change for NaN, Infs float->int conversion

2009/1/25 Matthew Brett : > When converting arrays from float to ints, I notice that NaNs, Infs, > and -Infs all get the minimum integer value: > flts = np.array([np.nan, np.inf, -np.inf]) flts.astype(np.int16) > array([-32768, -32768, -32768], dtype=int16) > > However, setting NaNs into

Re: [Numpy-discussion] numpy and the ACML

Hmmm. I'm at a bit of a loss to understand why it isn't working for you. How is it failing ?-- is the output of python setup.py build simply giving blas not found, or is it something more complex? Did you remove the previous build directory, and the previous install directory? Have you changed t

Re: [Numpy-discussion] glibc error

David Cournapeau wrote: > Hoyt Koepke wrote: > Actually, I would advise using only 3.8.2. Previous versions had bugs > for some core routines used by numpy (at least 3.8.0 did). I am a bit > surprised that a 64 bits-built atlas would be runnable at all in a 32 > bits binary - I would expect the

[Numpy-discussion] Suggested change for NaN, Infs float->int conversion

Hi, When converting arrays from float to ints, I notice that NaNs, Infs, and -Infs all get the minimum integer value: >>> flts = np.array([np.nan, np.inf, -np.inf]) >>> flts.astype(np.int16) array([-32768, -32768, -32768], dtype=int16) However, setting NaNs into integer arrays gives a value of 0