[Numpy-discussion] how to use masked arrays

2008-05-13 Thread Christopher Burns
I'm finding it difficult to tell which methods/operations respect the mask and which do not, in masked arrays. mydata.filled returns a copy of the data (in a numpy array) with all masked elements set to the fill_value. So, masked respected, but data returned as a new data-type when what I wanted

Re: [Numpy-discussion] ticket 788: possible blocker

2008-05-13 Thread Matthieu Brucher
2008/5/14 Matthew Brett <[EMAIL PROTECTED]>: > Hi, > > > Stefan, sometimes the fix really is clear and a test is like closing the > > barn door after the horse has bolted. Sometimes it isn't even clear *how* > to > > test. I committed one fix and omitted a test because I couldn't think of > > anyt

Re: [Numpy-discussion] Trac internal error

2008-05-13 Thread Jarrod Millman
On Tue, May 13, 2008 at 1:37 AM, Pauli Virtanen <[EMAIL PROTECTED]> wrote: > Something seems to be wrong with the Trac: > > http://scipy.org/scipy/numpy/timeline > > Internal Error > Ticket changes event provider (TicketModule) failed: > > SubversionException: ("Can't open file > '/home/scipy

Re: [Numpy-discussion] 1.1 dev on the trunk and the road to 1.2

2008-05-13 Thread Eric Firing
Jarrod Millman wrote: > On Tue, May 13, 2008 at 9:39 PM, Charles R Harris > <[EMAIL PROTECTED]> wrote: >> I was getting ready to add a big code cleanup, so you lucked out ;) Let's >> get this release out as quickly as possible once masked arrays are ready to >> go. > > What is left to do for the m

Re: [Numpy-discussion] 1.1 dev on the trunk and the road to 1.2

2008-05-13 Thread Jarrod Millman
On Tue, May 13, 2008 at 9:39 PM, Charles R Harris <[EMAIL PROTECTED]> wrote: > I was getting ready to add a big code cleanup, so you lucked out ;) Let's > get this release out as quickly as possible once masked arrays are ready to > go. What is left to do for the masked arrays? Just want to make

Re: [Numpy-discussion] 1.1 dev on the trunk and the road to 1.2

2008-05-13 Thread Charles R Harris
On Tue, May 13, 2008 at 7:39 PM, Jarrod Millman <[EMAIL PROTECTED]> wrote: > Hello, > > Well it has become obvious that I branched way too soon. My bad. So > I removed the branch: > http://projects.scipy.org/scipy/numpy/changeset/5163 > And updated the version.py to reflect that the trunk is sti

Re: [Numpy-discussion] gcov testing of C extensions (was Going toward time-based release ?)

2008-05-13 Thread David Cournapeau
Stéfan van der Walt wrote: > > Unless anybody points out a technical reason not to, please do have a > go at it -- the results are eagerly anticipated! > For numpy, it may be doable, but for scipy, it will be difficult, I think. In particular, statically linking c++ code is not easy. Is gcov

Re: [Numpy-discussion] searchsorted() and memory cache

2008-05-13 Thread Andrew Straw
Nathan Bell wrote: > On Tue, May 13, 2008 at 6:59 PM, Andrew Straw <[EMAIL PROTECTED]> wrote: > >> easier and still blazingly fast compared to the binary search >> implemented in searchsorted() given today's cached memory architectures. >> > > Andrew, I looked at your code and I don't qui

Re: [Numpy-discussion] searchsorted() and memory cache

2008-05-13 Thread Nathan Bell
On Tue, May 13, 2008 at 6:59 PM, Andrew Straw <[EMAIL PROTECTED]> wrote: > easier and still blazingly fast compared to the binary search > implemented in searchsorted() given today's cached memory architectures. Andrew, I looked at your code and I don't quite understand something. Why are you lo

[Numpy-discussion] 1.1 dev on the trunk and the road to 1.2

2008-05-13 Thread Jarrod Millman
Hello, Well it has become obvious that I branched way too soon. My bad. So I removed the branch: http://projects.scipy.org/scipy/numpy/changeset/5163 And updated the version.py to reflect that the trunk is still for 1.1 development: http://projects.scipy.org/scipy/numpy/changeset/5164 Sorry for

Re: [Numpy-discussion] searchsorted() and memory cache

2008-05-13 Thread Andrew Straw
Charles R Harris wrote: > > > On Tue, May 13, 2008 at 5:59 PM, Andrew Straw <[EMAIL PROTECTED] > > wrote: > > Thanks for all the comments on my original question. I was more > offline > than intended after I sent it until now, so I'm sorry I wasn't > immedi

Re: [Numpy-discussion] searchsorted() and memory cache

2008-05-13 Thread Charles R Harris
On Tue, May 13, 2008 at 5:59 PM, Andrew Straw <[EMAIL PROTECTED]> wrote: > Thanks for all the comments on my original question. I was more offline > than intended after I sent it until now, so I'm sorry I wasn't > immediately able to participate in the discussion. > > Anyhow, after working on this

Re: [Numpy-discussion] searchsorted() and memory cache

2008-05-13 Thread Andrew Straw
Thanks for all the comments on my original question. I was more offline than intended after I sent it until now, so I'm sorry I wasn't immediately able to participate in the discussion. Anyhow, after working on this a bit more, I came up with a few implementations of search algorithms doing just w

Re: [Numpy-discussion] ticket 788: possible blocker

2008-05-13 Thread Matthew Brett
Hi, > Stefan, sometimes the fix really is clear and a test is like closing the > barn door after the horse has bolted. Sometimes it isn't even clear *how* to > test. I committed one fix and omitted a test because I couldn't think of > anything really reasonable. I think concentrating on unit tests

Re: [Numpy-discussion] ticket 788: possible blocker

2008-05-13 Thread Charles R Harris
On Tue, May 13, 2008 at 4:40 PM, Stéfan van der Walt <[EMAIL PROTECTED]> wrote: > 2008/5/13 Travis E. Oliphant <[EMAIL PROTECTED]>: > > Robert Kern wrote: > > > On Tue, May 13, 2008 at 11:12 AM, Travis E. Oliphant > > > <[EMAIL PROTECTED]> wrote: > > > > > > > > >> Besides, having a "test-p

Re: [Numpy-discussion] gcov testing of C extensions (was Going toward time-based release ?)

2008-05-13 Thread Stéfan van der Walt
2008/5/13 Alan McIntyre <[EMAIL PROTECTED]>: > On Mon, May 12, 2008 at 3:09 AM, Stéfan van der Walt <[EMAIL PROTECTED]> > wrote: > > The much more important issue is > > having the C extensions tested, and if anyone can figure out a way to > > get gcov to generate those coverage reports, I'd

Re: [Numpy-discussion] ticket 788: possible blocker

2008-05-13 Thread Stéfan van der Walt
2008/5/13 Travis E. Oliphant <[EMAIL PROTECTED]>: > Robert Kern wrote: > > On Tue, May 13, 2008 at 11:12 AM, Travis E. Oliphant > > <[EMAIL PROTECTED]> wrote: > > > > > >> Besides, having a "test-per-checkin" is not the proper mapping in my > >> mind. I'd rather see whole check-ins devot

Re: [Numpy-discussion] ticket 788: possible blocker

2008-05-13 Thread Eric Firing
Travis E. Oliphant wrote: > Robert Kern wrote: >> On Tue, May 13, 2008 at 11:12 AM, Travis E. Oliphant >> <[EMAIL PROTECTED]> wrote: >> >> >>> Besides, having a "test-per-checkin" is not the proper mapping in my >>> mind. I'd rather see whole check-ins devoted to testing large pieces >>> o

[Numpy-discussion] numpy with icc

2008-05-13 Thread Erik Nugent
I am trying to build numpy with intel icc and mkl. I don't understand a lot of what I am doing. I have followed the the suggestions of what to add/change in site.cfg intelccompiler.py and system_info.py from several different posts or google searches. i am not sure i have done any of this right.

Re: [Numpy-discussion] ticket 788: possible blocker

2008-05-13 Thread Travis E. Oliphant
Charles R Harris wrote: > > > On Tue, May 13, 2008 at 11:25 AM, Robert Kern <[EMAIL PROTECTED] > > wrote: > > On Tue, May 13, 2008 at 11:12 AM, Travis E. Oliphant > <[EMAIL PROTECTED] > wrote: > > > Besides, having a "test-per-check

Re: [Numpy-discussion] ticket 788: possible blocker

2008-05-13 Thread Travis E. Oliphant
Robert Kern wrote: > On Tue, May 13, 2008 at 11:12 AM, Travis E. Oliphant > <[EMAIL PROTECTED]> wrote: > > >> Besides, having a "test-per-checkin" is not the proper mapping in my >> mind. I'd rather see whole check-ins devoted to testing large pieces >> of code rather than spend all unit-t

Re: [Numpy-discussion] ticket 788: possible blocker

2008-05-13 Thread Charles R Harris
On Tue, May 13, 2008 at 11:25 AM, Robert Kern <[EMAIL PROTECTED]> wrote: > On Tue, May 13, 2008 at 11:12 AM, Travis E. Oliphant > <[EMAIL PROTECTED]> wrote: > > > Besides, having a "test-per-checkin" is not the proper mapping in my > > mind. I'd rather see whole check-ins devoted to testing l

Re: [Numpy-discussion] ticket 788: possible blocker

2008-05-13 Thread Robert Kern
On Tue, May 13, 2008 at 11:12 AM, Travis E. Oliphant <[EMAIL PROTECTED]> wrote: > Besides, having a "test-per-checkin" is not the proper mapping in my > mind. I'd rather see whole check-ins devoted to testing large pieces > of code rather than spend all unit-test foo on a rigid policy of >

[Numpy-discussion] gcov testing of C extensions (was Going toward time-based release ?)

2008-05-13 Thread Alan McIntyre
On Mon, May 12, 2008 at 3:09 AM, Stéfan van der Walt <[EMAIL PROTECTED]> wrote: > The much more important issue is > having the C extensions tested, and if anyone can figure out a way to > get gcov to generate those coverage reports, I'd be in the seventh > heaven. Thus far, the only way I kno

Re: [Numpy-discussion] ticket 788: possible blocker

2008-05-13 Thread Travis E. Oliphant
Stéfan van der Walt wrote: > Hi Travis > > 2008/5/13 Travis E. Oliphant <[EMAIL PROTECTED]>: > >> I think Stefan is asking me, not you.I don't think you should feel >> any sense of guilt. I was the one who closed the ticket sans >> regression test. I tend to still be of the opinion th

Re: [Numpy-discussion] Going toward time-based release ?

2008-05-13 Thread Matthieu Brucher
> > > > I tried something similar with figleaf on my own code, but it seems that > > every test that is decorated with @raises is not tested. Does your > coverage > > include these tests ? I didn't change much of your script to do it. > > I tried the pinocchio nose extension as well, but it seems

Re: [Numpy-discussion] Array finalize call from std/var?

2008-05-13 Thread Pierre GM
On Tuesday 13 May 2008 09:08:18 ctw wrote: > Basically, it seems that __array_finalize__ is called after calls to > most functions (such as mean), but not after calls to std or var. Mmh, it's not exactly how I understand: in fact, __array_finalize__ seems to be called an extra time with the ndar

[Numpy-discussion] Array finalize call from std/var?

2008-05-13 Thread ctw
Hi! Does anybody here know what's going on in the situation described in this ticket? http://scipy.org/scipy/numpy/ticket/791 Basically, it seems that __array_finalize__ is called after calls to most functions (such as mean), but not after calls to std or var. Thanks! CTW ___

Re: [Numpy-discussion] Going toward time-based release ?

2008-05-13 Thread Stéfan van der Walt
Hi Matthieu 2008/5/13 Matthieu Brucher <[EMAIL PROTECTED]>: > > As for the NumPy unit tests: I have placed coverage reports online > > (http://mentat.za.net/numpy/coverage). This only covers Python (not > > extension) code, but having that part 100% tested is not impossible, > > nor would it take

Re: [Numpy-discussion] Going toward time-based release ?

2008-05-13 Thread Matthieu Brucher
> > As for the NumPy unit tests: I have placed coverage reports online > (http://mentat.za.net/numpy/coverage). This only covers Python (not > extension) code, but having that part 100% tested is not impossible, > nor would it take that much effort. The much more important issue is > having the C

Re: [Numpy-discussion] "API change" or "stuff we'd like to change" was: recarray fun

2008-05-13 Thread Jarrod Millman
On Tue, May 13, 2008 at 2:31 AM, Sebastian Haase <[EMAIL PROTECTED]> wrote: > as a summary of many more "smaller" things, such as > * np.resize vs. arr.resize need unified behavior, and additional > argument to allow old behavior I think you are asking about whether you can start discussing s

[Numpy-discussion] "API change" or "stuff we'd like to change" was: recarray fun

2008-05-13 Thread Sebastian Haase
On Thu, May 1, 2008 at 10:02 PM, Alan G Isaac <[EMAIL PROTECTED]> wrote: > On Thu, 01 May 2008, Christopher Barker apparently wrote: > > Maybe we should have a Wiki page for "stuff we'd like to change, but > > won't until major API breakage is otherwise occurring" > > > Perhaps http://www.scipy.

Re: [Numpy-discussion] Trac internal error

2008-05-13 Thread Jarrod Millman
On Tue, May 13, 2008 at 1:37 AM, Pauli Virtanen <[EMAIL PROTECTED]> wrote: > Something seems to be wrong with the Trac: Yes, I know. I already sent an email to Peter Wang. There are a few files whose ownership got changed and it will be fixed by the morning. Thanks, -- Jarrod Millman Computa

[Numpy-discussion] Trac internal error

2008-05-13 Thread Pauli Virtanen
Hi, Something seems to be wrong with the Trac: http://scipy.org/scipy/numpy/timeline Internal Error Ticket changes event provider (TicketModule) failed: SubversionException: ("Can't open file '/home/scipy/svn/numpy/db/revprops/5159': Permission denied", 13) -- Pauli Virtanen ___