Re: [Numpy-discussion] Time for beta1 of NumPy 1.0

2006-06-29 Thread Stephan Tolksdorf
I guess this is a change which would just break too much code. And if the default type should by changed for these functions, why not also for array constructors? On the other hand, many people probably use Numpy almost exclusively with Float64's. A convenient way to change the default type c

[Numpy-discussion] logspace behaviour/documentation

2006-06-29 Thread Arnd Baecker
Hi, I am wondering a bit about the the behaviour of logspace: Definition: numpy.logspace(start, stop, num=50, endpoint=True, base=10.0) Reading this I would assume that numpy.logspace(10**-12, 0.0, 100) gives 100 values, from start=10**-12 to stop=0.0, equispaced on a logarithmic scale. But t

Re: [Numpy-discussion] Time for beta1 of NumPy 1.0

2006-06-29 Thread Keith Goodman
On 6/29/06, Bill Baxter <[EMAIL PROTECTED]> wrote: > Rand at least returns doubles: > > >>> num.rand(3,3).dtype.name > 'float64' Then I vote float64. >> linalg.eigh(asmatrix(1))[0].dtype.name 'float64' >> linalg.cholesky(asmatrix(1)).dtype.name 'float64' Using Tomcat but need to do more? Need t

Re: [Numpy-discussion] Time for beta1 of NumPy 1.0

2006-06-29 Thread Bill Baxter
Rand at least returns doubles:>>> num.rand(3,3).dtype.name'float64'--bbOn 6/30/06, Keith Goodman < [EMAIL PROTECTED]> wrote:On 6/29/06, Bill Baxter < [EMAIL PROTECTED]> wrote:> I also find the int behavior of these functions strange.>> +1 float default (or double)Oh, wait. Which do I want, float or

Re: [Numpy-discussion] Time for beta1 of NumPy 1.0

2006-06-29 Thread Keith Goodman
On 6/29/06, Bill Baxter <[EMAIL PROTECTED]> wrote: > I also find the int behavior of these functions strange. > > +1 float default (or double) Oh, wait. Which do I want, float or double? What does rand, eigh, lstsq, etc return? Using Tomcat but need to do more? Need to support web services, secur

Re: [Numpy-discussion] Time for beta1 of NumPy 1.0

2006-06-29 Thread Bill Baxter
I also find the int behavior of these functions strange.+1 float default (or double)--bbOn 6/30/06, Tim Leslie < [EMAIL PROTECTED]> wrote:On 6/30/06, Keith Goodman < [EMAIL PROTECTED]> wrote:> On 6/29/06, Alan G Isaac <[EMAIL PROTECTED]> wrote:> > A rather minor issue, but I would just like to make

Re: [Numpy-discussion] Time for beta1 of NumPy 1.0

2006-06-29 Thread Sasha
I vote for no change. It will be a major backward compatibility headache with applications that rely on integer arrays breaking in mysterious ways. If float wins, I hope there will be a script to update old code. Detecting single argument calls to these functions is probably not very hard. On 6/2

Re: [Numpy-discussion] Time for beta1 of NumPy 1.0

2006-06-29 Thread Tim Leslie
On 6/30/06, Keith Goodman <[EMAIL PROTECTED]> wrote: > On 6/29/06, Alan G Isaac <[EMAIL PROTECTED]> wrote: > > A rather minor issue, but I would just like to make sure > > that a policy decision was made not to move to a float > > default for identity(), ones(), zeros(), and empty(). > > (I leave a

Re: [Numpy-discussion] Time for beta1 of NumPy 1.0

2006-06-29 Thread Keith Goodman
On 6/29/06, Alan G Isaac <[EMAIL PROTECTED]> wrote: > On Thu, 29 Jun 2006, Travis Oliphant apparently wrote: > > Please make any comments or voice major concerns > > A rather minor issue, but I would just like to make sure > that a policy decision was made not to move to a float > default for ident

Re: [Numpy-discussion] Time for beta1 of NumPy 1.0

2006-06-29 Thread Alan G Isaac
On Thu, 29 Jun 2006, Travis Oliphant apparently wrote: > Please make any comments or voice major concerns A rather minor issue, but I would just like to make sure that a policy decision was made not to move to a float default for identity(), ones(), zeros(), and empty(). (I leave aside arange(

[Numpy-discussion] Time for beta1 of NumPy 1.0

2006-06-29 Thread Travis Oliphant
I think it's time for the first beta-release of NumPy 1.0 I'd like to put it out within 2 weeks. Please make any comments or voice major concerns so that the 1.0 release series can be as stable as possible. -Travis Using Tomcat but need to do more? Need to support web services, security? Get

Re: [Numpy-discussion] Core dump in numpy 0.9.6

2006-06-29 Thread Robert Kern
Robert Lupton wrote: > Here's an easy coredump: > > x = numpy.arange(10, dtype="f"); y = numpy.array(len(x), dtype="F"); > y.imag += x > > Program received signal EXC_BAD_ACCESS, Could not access memory. This bug does not appear to exist in recent versions. Please try the latest release (and

[Numpy-discussion] Core dump in numpy 0.9.6

2006-06-29 Thread Robert Lupton
Here's an easy coredump: x = numpy.arange(10, dtype="f"); y = numpy.array(len(x), dtype="F"); y.imag += x Program received signal EXC_BAD_ACCESS, Could not access memory. Reason: KERN_PROTECTION_FAILURE at address: 0x PyArray_CompareLists (l1=0x0, l2=0x1841618, n=1) at numpy/core/src/

[Numpy-discussion] python spherepack wrapper

2006-06-29 Thread Jeff Whitaker
Hi All: For those of you who have a need for spherical harmonic transforms in python, I've updated my spherepack (http://www.cisl.ucar.edu/css/software/spherepack/) wrapper for numpy. Docs at http://www.cdc.noaa.gov/people/jeffrey.s.whitaker/python/spharm.html. If you have numpy and a fortr

[Numpy-discussion] We *will* move the mailing list to scipy.org

2006-06-29 Thread Robert Kern
With a vote of 14 to 2 (and about 400 hundred implicit "I don't care one way or the other"), the new ads, and the recent problems with Sourceforge bouncing or delaying GMail messages, I intend to move the mailing list from Sourceforge to scipy.org in short order. If you have strong objections t

Re: [Numpy-discussion] incorporating C/C++ code

2006-06-29 Thread Tim Hochberg
Christopher Barker wrote: > Louis Cordier wrote: > >>> At this point I would not use SWIG or Instant. >>> > > In general, SWIG makes sense if you have a substantial existing library > that you need access to, and particularly if that library is evolving > and needs to be used directly f

Re: [Numpy-discussion] incorporating C/C++ code

2006-06-29 Thread Philip Austin
Christopher Barker writes: > If you are writing C/C++ code specifically to be used as a python > extension, pyrex and boost::python are good choices. There was a Numeric > add-on to boost::python at one point, I don't know if anyone has > modified it for numpy. Yes, I've been migrating my

Re: [Numpy-discussion] Sourceforge and gmail [was: Re: Recarray attributes writeable]

2006-06-29 Thread David Huard
Is it possible that gmail mails get through when they are sent by lists.sourceforge.netwhile they are blocked when the outgoing server is gmail.com ? My situation is that I can't post a new discussion to the list, although replies seem to get through.David2006/6/16, Robert Kern < [EMAIL PROTECTED]

Re: [Numpy-discussion] incorporating C/C++ code

2006-06-29 Thread Christopher Barker
Louis Cordier wrote: >> At this point I would not use SWIG or Instant. In general, SWIG makes sense if you have a substantial existing library that you need access to, and particularly if that library is evolving and needs to be used directly from C/C++ code as well. If you are writing C/C++ co

Re: [Numpy-discussion] min/max not exported in "from numpy import *"

2006-06-29 Thread Christopher Barker
Travis Oliphant wrote: > Well, Numeric had the sum function long before Python introduced one. > NumPy adopted Numeric's sum function as well. Yet another reason to NEVER use "import *" -CHB -- Christopher Barker, Ph.D. Oceanographer NOAA/OR

[Numpy-discussion] Bug in digitize function

2006-06-29 Thread David Huard
Hi, Here is something I noticed with digitize() that I guess would qualify as a small but annoying bug. In [165]: x = rand(10); bin = linspace(x.min(), x.max(), 10); print x.min(); print bin[0]; digitize(x,bin) 0.09250301841440.0925030184144Out[165]: array([2, 9, 5, 9, 6, 1, 1, 1, 4, 5])In [166]: x

Re: [Numpy-discussion] incorporating C/C++ code

2006-06-29 Thread Louis Cordier
>> For heavy number crunching I would like to include C and/or C++ functions >> in my NumPy programs. They should have/give NumPy arrays as input/output. >> On http://www.scipy.org/Topical_Software I find several suggestions to wrap >> C/C++ code: SWIG, weave, Pyrex, Instant, ... but it's quite di

Re: [Numpy-discussion] incorporating C/C++ code

2006-06-29 Thread Travis Oliphant
Joris De Ridder wrote: > Hi, > > For heavy number crunching I would like to include C and/or C++ functions > in my NumPy programs. They should have/give NumPy arrays as input/output. > On http://www.scipy.org/Topical_Software I find several suggestions to wrap > C/C++ code: SWIG, weave, Pyrex, Ins

Re: [Numpy-discussion] trouble on tru64

2006-06-29 Thread N Shimizu
Thank you for your reply. The "config.h" is the following. I hope it will be helpful. Shimizu /* #define SIZEOF_SHORT 2 */ /* #define SIZEOF_INT 4 */ /* #define SIZEOF_LONG 8 */ /* #define SIZEOF_FLOAT 4 */ /* #define SIZEOF_DOUBLE 8 */ #define SIZEOF_LONG_DOUBLE 16 #define SIZEOF_PY_INTPTR_T 8 /

Re: [Numpy-discussion] min/max not exported in "from numpy import *"

2006-06-29 Thread Travis Oliphant
Zhang Le wrote: >> I'm going to take a wild-ass guess and suggest that was a concious decision >> by the authors. Shadowing builtins is generally a no-no. You just need to >> be explicit instead of implicit: >> >> from numpy import min, max >> > I see. But why by default sum is exported?

Re: [Numpy-discussion] trouble on tru64

2006-06-29 Thread Travis Oliphant
N Shimizu wrote: > Hi everyone, > > I tried to build numpy 0.9.8 on compaq alpha tru64 UNIX v5.1 with gcc 4.0.2, > > but I encounterd the compilation trouble. > Thanks for the test. This looks like a configuration problem. Could you post the config.h file that is generated when you ru

[Numpy-discussion] trouble on tru64

2006-06-29 Thread N Shimizu
Hi everyone, I tried to build numpy 0.9.8 on compaq alpha tru64 UNIX v5.1 with gcc 4.0.2, but I encounterd the compilation trouble. The error message is the following. Do you have any suggestion? Thank you in advance. Shimizu. numpy/core/src/umathmodule.c.src: In function 'nc_floor_quotl': num

Re: [Numpy-discussion] incorporating C/C++ code

2006-06-29 Thread Rob Hooft
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Joris De Ridder wrote: > Hi, > > For heavy number crunching I would like to include C and/or C++ functions > in my NumPy programs. They should have/give NumPy arrays as input/output. > On http://www.scipy.org/Topical_Software I find several suggestio

[Numpy-discussion] incorporating C/C++ code

2006-06-29 Thread Joris De Ridder
Hi, For heavy number crunching I would like to include C and/or C++ functions in my NumPy programs. They should have/give NumPy arrays as input/output. On http://www.scipy.org/Topical_Software I find several suggestions to wrap C/C++ code: SWIG, weave, Pyrex, Instant, ... but it's quite difficult

Re: [Numpy-discussion] min/max not exported in "from numpy import *"

2006-06-29 Thread Jeff Whitaker
Zhang Le wrote: >> I'm going to take a wild-ass guess and suggest that was a concious decision >> by the authors. Shadowing builtins is generally a no-no. You just need to >> be explicit instead of implicit: >> >> from numpy import min, max >> > I see. But why by default sum is exported?

Re: [Numpy-discussion] Should cholesky return upper or

2006-06-29 Thread Jon Wright
> Does it matter whether the lower or upper triangular part is stored? > We should just pick one convention and stick with it. That is simpler > than, say, ATLAS where the choice is one of the parameters passed to > the subroutine. I vote for lower triangular myself, if only because > that was

Re: [Numpy-discussion] min/max not exported in "from numpy import *"

2006-06-29 Thread Zhang Le
> I'm going to take a wild-ass guess and suggest that was a concious decision > by the authors. Shadowing builtins is generally a no-no. You just need to > be explicit instead of implicit: > > from numpy import min, max I see. But why by default sum is exported? Is that a wise decision? In [

Re: [Numpy-discussion] min/max not exported in "from numpy import *"

2006-06-29 Thread skip
Zhang> I'm using 0.9.8 and find numpy.ndarray.min() is not exported to Zhang> global space when doing a Zhang> from numpy import * I'm going to take a wild-ass guess and suggest that was a concious decision by the authors. Shadowing builtins is generally a no-no. You just need t

[Numpy-discussion] min/max not exported in "from numpy import *"

2006-06-29 Thread Zhang Le
Hi, I'm using 0.9.8 and find numpy.ndarray.min() is not exported to global space when doing a from numpy import * In [1]: from numpy import * In [2]: help min --> help(min) Help on built-in function min in module __builtin__: min(...) min(sequence) -> value min(a, b, c, ...) -> va

[Numpy-discussion] explanation of 'order' parameter for reshape

2006-06-29 Thread Glen W. Mabey
Hello, It seems that the 'order' parameter is not explained neither in the docstring nor in "Guide to NumPy". I'm guessing that the alternative to the default value of 'C' would be 'Fortran'? Thanks, Glen Using Tomcat but need to do more? Need to support web services, security? Get stuff done

Re: [Numpy-discussion] Should cholesky return upper or lowertriangularmatrix?

2006-06-29 Thread Charles R Harris
All,On 6/29/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: The SAS IML Cholesky function "root" returns upper triangular.  Quoting theSAS documentation:The ROOT function performs the Cholesky decomposition of a matrix (forexample, A) such thatU'U = A where U is upper triangular. The matrix A must

Re: [Numpy-discussion] Should cholesky return upper or lowertriangularmatrix?

2006-06-29 Thread mfmorss
The SAS IML Cholesky function "root" returns upper triangular. Quoting the SAS documentation: The ROOT function performs the Cholesky decomposition of a matrix (for example, A) such that U'U = A where U is upper triangular. The matrix A must be symmetric and positive definite. Mark F. Morss Prin