Re: [Numpy-discussion] numpy.ma.compress

2008-01-23 Thread Travis E. Oliphant
Pierre GM wrote: > Oh, a last comment question: > Is the current documentation standard definitive ? Yes. -Travis ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] numpy.ma.compress

2008-01-23 Thread Pierre GM
All, I just committed a fix on the SVN. Now, the axis keyword should be recognized. Sorry for the delay. Pierre ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] where() on mac/pc return different things

2008-01-23 Thread James Battat
Robert, Thanks for solving that puzzle! I'll get our group on the same 1.0.x numpy release. Take care, James ** Harvard University Dept. of Astronomy 60 Garden Street MS-10 Cambridge, MA 02138 phone 617.496.5988 lab 617.495.3267 email [EMAIL PROTECTED] web http://www

Re: [Numpy-discussion] where() on mac/pc return different things

2008-01-23 Thread Robert Kern
James Battat wrote: > Hi, > > numpy.where() returns different things on my windowsXP machine than on my > collaborator's mac osx machine. > > For example, consider: > >>> import numpy > >>> a = numpy.array([1,2,3,4]) > >>> b = numpy.where( a > 2 ) > > On WindowsXP (python 2.4.2, numpy 1.0.

[Numpy-discussion] where() on mac/pc return different things

2008-01-23 Thread James Battat
Hi, numpy.where() returns different things on my windowsXP machine than on my collaborator's mac osx machine. For example, consider: >>> import numpy >>> a = numpy.array([1,2,3,4]) >>> b = numpy.where( a > 2 ) On WindowsXP (python 2.4.2, numpy 1.0.1), I get: >>> print b (array([2, 3]),

Re: [Numpy-discussion] numpy.ma.compress

2008-01-23 Thread Pierre GM
Oh, a last comment question: Is the current documentation standard definitive ? It seems to have changed in the last few weeks (I haven't really followed what happened). If yes, I'll try to correct the current SVN version, but that may take a little while... __

Re: [Numpy-discussion] numpy.ma.compress

2008-01-23 Thread Pierre GM
On Wednesday 23 January 2008 17:05:25 Stefan van der Walt wrote: > On Wed, Jan 23, 2008 at 11:17:51AM -1000, Eric Firing wrote: > > Pierre, > > > > numpy.compress exists, but numpy.ma.compress does not; is this > > intentional? > > Looks like x.compress exists, but it doesn't work as expected: > >

Re: [Numpy-discussion] planet.scipy.org

2008-01-23 Thread Barry Wark
thanks. On Jan 22, 2008 10:04 PM, Jarrod Millman <[EMAIL PROTECTED]> wrote: > On Jan 18, 2008 11:17 PM, Barry Wark <[EMAIL PROTECTED]> wrote: > > I promise: last change. I changed the URL to > > http://physionconsulting.blogspot.com/search/label/scipy. My wife said > > physion consultants is a cra

Re: [Numpy-discussion] numpy.ma.compress

2008-01-23 Thread Eric Firing
Pierre GM wrote: > On Wednesday 23 January 2008 16:17:51 you wrote: >> Pierre, >> >> numpy.compress exists, but numpy.ma.compress does not; is this intentional? > > Probably not. I usually don't use this function, preferring to use indexing > instead. If you have a need for it, I can probably com

Re: [Numpy-discussion] numpy.ma.compress

2008-01-23 Thread Stefan van der Walt
Hi Eric, On Wed, Jan 23, 2008 at 11:17:51AM -1000, Eric Firing wrote: > Pierre, > > numpy.compress exists, but numpy.ma.compress does not; is this > intentional? Thanks for the report. I added a simple implementation to SVN for the time being. Regards Stéfan ___

Re: [Numpy-discussion] numpy.ma.compress

2008-01-23 Thread Stefan van der Walt
On Wed, Jan 23, 2008 at 11:17:51AM -1000, Eric Firing wrote: > Pierre, > > numpy.compress exists, but numpy.ma.compress does not; is this > intentional? Looks like x.compress exists, but it doesn't work as expected: x = N.ma.array([1,2,3],mask=[True,False,Fals]) x.compress(x<2) throws ValueErr

[Numpy-discussion] numpy.ma.compress

2008-01-23 Thread Eric Firing
Pierre, numpy.compress exists, but numpy.ma.compress does not; is this intentional? Eric ___ Numpy-discussion mailing list Numpy-discussion@scipy.org http://projects.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] Sage/Scipy Days 8 reminder: Feb 29-March 4.

2008-01-23 Thread Fernando Perez
On Jan 23, 2008 12:09 PM, Chris Calloway <[EMAIL PROTECTED]> wrote: > Fernando Perez wrote: > > Just a quick reminder for all about the upcoming Sage/Scipy Days 8 at > > Enthought collaborative meeting: > > > > http://wiki.sagemath.org/days8 > > This page says "February 29 until March 4, *2007*."

Re: [Numpy-discussion] __array_interface__ / __array_struct__

2008-01-23 Thread Thomas Heller
Travis E. Oliphant schrieb: > Thomas Heller wrote: >> Travis E. Oliphant schrieb: >> >>> Thomas Heller wrote: >>> I am experimenting with implementing __array_interface__ and/or __array_struct__ properties for ctypes instances, and have problems to create numpy arrays f

Re: [Numpy-discussion] Sage/Scipy Days 8 reminder: Feb 29-March 4.

2008-01-23 Thread Chris Calloway
Fernando Perez wrote: > Just a quick reminder for all about the upcoming Sage/Scipy Days 8 at > Enthought collaborative meeting: > > http://wiki.sagemath.org/days8 This page says "February 29 until March 4, *2007*." -- Sincerely, Chris Calloway http://www.seacoos.org office: 332 Chapman Hall

Re: [Numpy-discussion] How to build on Solaris 10 (x86) using sunperf?

2008-01-23 Thread Peter Ward
David Cournapeau wrote: > The current config.h works fine for solaris with Sun compilers, in my > experience, so the problem must be somewhere else. > > Peter, could you post the errors you got ? As an alternative, I am > working on an alternative build system for numpy: it should work on > solari

Re: [Numpy-discussion] changed behavior of numpy.histogram

2008-01-23 Thread Mark.Miller
Nah...no worries Stuart. Again, I recognize that what I was doing deviated from the likely true intent of the histogram function. But it was a nice convenient bit of code, for sure. I'll take a look at your suggestion...it's different than what I previously used. So, thanks for the input. A

Re: [Numpy-discussion] changed behavior of numpy.histogram

2008-01-23 Thread Stuart Brorson
Hi again -- You made me feel guilty about breaking your code. Here's some suggested substitute code : In [10]: import numpy In [11]: a = numpy.array(('atcg', '', 'atcg', 'actg', '')) In [12]: b = numpy.sort(a) In [13]: c = numpy.unique(b) In [14]: d = numpy.searchsorted(b, c) In [1

Re: [Numpy-discussion] changed behavior of numpy.histogram

2008-01-23 Thread Travis E. Oliphant
Mark.Miller wrote: > Greetings: I just noticed a changed behavior of numpy.histogram. I > think that a recent 'fix' to the code has changed my ability to use that > function (albeit in an unconventional manner). I previously used the > histogram function to obtain counts of each unique string

Re: [Numpy-discussion] changed behavior of numpy.histogram

2008-01-23 Thread Stuart Brorson
Hi -- > Greetings: I just noticed a changed behavior of numpy.histogram. I > think that a recent 'fix' to the code has changed my ability to use that > function (albeit in an unconventional manner). You can blame me for this. I submitted a patch which prohibited the user from entering any rang

[Numpy-discussion] changed behavior of numpy.histogram

2008-01-23 Thread Mark.Miller
Greetings: I just noticed a changed behavior of numpy.histogram. I think that a recent 'fix' to the code has changed my ability to use that function (albeit in an unconventional manner). I previously used the histogram function to obtain counts of each unique string within a string array. A

Re: [Numpy-discussion] Docstring standard: how to specify variable types

2008-01-23 Thread Charles R Harris
On Jan 23, 2008 6:55 AM, Stefan van der Walt <[EMAIL PROTECTED]> wrote: > Hi all, > > The numpy documentation standard example shows: > >Parameters >-- >var1 : array_like >Array_like means all those objects -- lists, nested lists, etc. -- >that can be converted

[Numpy-discussion] [ANN] numscons 0.3.0 release

2008-01-23 Thread David Cournapeau
Hi, I've just released the 0.3.0 release of numscons, an alternative build system for numpy. The tarballs are available on launchpad. https://launchpad.net/numpy.scons.support/0.3/0.3.0 To use it, you need to get the build_with_scons numpy branch: see http://projects.scipy.org/scipy/numpy/

[Numpy-discussion] Docstring standard: how to specify variable types

2008-01-23 Thread Stefan van der Walt
Hi all, The numpy documentation standard example shows: Parameters -- var1 : array_like Array_like means all those objects -- lists, nested lists, etc. -- that can be converted to an array. var2 : integer Write out the full type long_variable_na

Re: [Numpy-discussion] data type specifications

2008-01-23 Thread Gary Pajer
On Jan 23, 2008 2:48 AM, Stefan van der Walt <[EMAIL PROTECTED]> wrote: > Hi Gary > > On Tue, Jan 22, 2008 at 11:18:01AM -0500, Gary Pajer wrote: > > Occasionally I find myself poking into docstrings and googling > > randomly trying to find the proper way to specify a data type, or > > trying to re

[Numpy-discussion] ndarray.__mul__ is too gready?

2008-01-23 Thread Pearu Peterson
Hi, Say, one defines a class A that does not like to have numpy arrays in the left-hand-side of an operation, say *, but in the rhs it is expected. For an example, consider A as a huge customized matrix that defines only matrix * vector where vector can be numpy array and scalar * matrix where sc

Re: [Numpy-discussion] How to build on Solaris 10 (x86) using sunperf?

2008-01-23 Thread David Cournapeau
On Jan 23, 2008 12:32 PM, David Cournapeau <[EMAIL PROTECTED]> wrote: > > The current config.h works fine for solaris with Sun compilers, in my > experience, so the problem must be somewhere else. I've just tried numpy SVN with sun compiler (Sun studio 12) on Indiana, and it works fine, so there

Re: [Numpy-discussion] location of ma in maskedarray branch

2008-01-23 Thread Stefan van der Walt
Hi Matt On Tue, Jan 22, 2008 at 10:37:29PM -0500, Matt Knox wrote: > I noticed that the new masked array module resides in numpy/ma in the > maskedarray branch as opposed to numpy/core/ma like it does in the current > trunk. Was this intentional? Code that explicitly imports ma from the core > s