Re: [Numpy-discussion] The risks of empty()

2007-01-02 Thread A. M. Archibald
On 02/01/07, Bock, Oliver BGI SYD <[EMAIL PROTECTED]> wrote: > Some of my arrays are not fully populated. (I separately record which > entries are valid.) I want to use numpy.empty() to speed up the > creation of these arrays, but I'm worried about what will happen if I > apply operations to the

Re: [Numpy-discussion] The risks of empty()

2007-01-02 Thread Tim Hochberg
Bock, Oliver BGI SYD wrote: > Some of my arrays are not fully populated. (I separately record which > entries are valid.) I want to use numpy.empty() to speed up the > creation of these arrays, but I'm worried about what will happen if I > apply operations to the entire contents of these arrays.

Re: [Numpy-discussion] The risks of empty()

2007-01-02 Thread Robert Kern
Bock, Oliver BGI SYD wrote: > Some of my arrays are not fully populated. (I separately record which > entries are valid.) I want to use numpy.empty() to speed up the > creation of these arrays, but I'm worried about what will happen if I > apply operations to the entire contents of these arrays.

[Numpy-discussion] The risks of empty()

2007-01-02 Thread Bock, Oliver BGI SYD
Some of my arrays are not fully populated. (I separately record which entries are valid.) I want to use numpy.empty() to speed up the creation of these arrays, but I'm worried about what will happen if I apply operations to the entire contents of these arrays. E.g. a + b I care about the resul