Re: [Numpy-discussion] issue #1431 accessing multiple fields in a recarray

On Sun, Jun 27, 2010 at 8:26 AM, sam tygier wrote: > Hello > > A while ago there was a discussion about field order when accessing > recarrays. eg: > x = np.array([(1.5,2.5,(1.0,2.0)),(3.,4.,(4.,5.)),(1.,3.,(2.,6.))], >         dtype=[('x','f4'),('y',np.float32),('value','f4',(2,2))]) x

Re: [Numpy-discussion] printing of array and leading white space ?

I don't know precisely how the decision is made, but in general one needs the pad spaces for printing arrays with > 1 row. Friedrich 2010/6/26 Vincent Davis : > This is a little strange and I am not sure what is going on. Look at > the number of spaced before the first number in the array. >

Re: [Numpy-discussion] arr.copy(order='F') doesn't agree with docstring: what is intended behavior?

Sun, 27 Jun 2010 13:41:23 -0500, Kurt Smith wrote: [clip] > I misspoke (mistyped...). So long as it has the 'F' behavior I'm happy, > and I'll gladly file a bug report & patch to get the code to match the > docs, assuming that's the intended behavior. The problem is probably that the function is

Re: [Numpy-discussion] arr.copy(order='F') doesn't agree with docstring: what is intended behavior?

On Sun, Jun 27, 2010 at 1:03 PM, David Goldsmith wrote: > On Sun, Jun 27, 2010 at 10:38 AM, Kurt Smith wrote: >> >> On Sat, Jun 26, 2010 at 7:34 PM, Warren Weckesser >> wrote: >> > Kurt Smith wrote: >> >> I'd really like arr.copy(order='F') to work -- is it supposed to as >> >> its docstring say

Re: [Numpy-discussion] numpy.random.poisson docs missing "Returns"

On Sun, Jun 27, 2010 at 3:44 AM, Pauli Virtanen wrote: > Sat, 26 Jun 2010 17:37:22 -0700, David Goldsmith wrote: > > On Sat, Jun 26, 2010 at 3:22 PM, wrote: > [clip] > >> Is there a chance that some changes got lost? > > > > (Almost) anything's possible... :-( > > There's practically no change o

Re: [Numpy-discussion] arr.copy(order='F') doesn't agree with docstring: what is intended behavior?

On Sun, Jun 27, 2010 at 10:38 AM, Kurt Smith wrote: > On Sat, Jun 26, 2010 at 7:34 PM, Warren Weckesser > wrote: > > Kurt Smith wrote: > >> I'd really like arr.copy(order='F') to work -- is it supposed to as > >> its docstring says, or is it supposed to raise a TypeError as it does > >> now? > >

Re: [Numpy-discussion] Strange behavior of np.sinc

On Sat, Jun 26, 2010 at 10:00 PM, David Goldsmith wrote: > On Sat, Jun 26, 2010 at 9:39 PM, Robert Kern wrote: > >> On Sat, Jun 26, 2010 at 23:33, David Goldsmith >> wrote: >> > Hi! The docstring for numpy.lib.function_base.sinc indicates that the >> > parameter has to be an ndarray, and that it

Re: [Numpy-discussion] arr.copy(order='F') doesn't agree with docstring: what is intended behavior?

On Sat, Jun 26, 2010 at 7:34 PM, Warren Weckesser wrote: > Kurt Smith wrote: >> I'd really like arr.copy(order='F') to work -- is it supposed to as >> its docstring says, or is it supposed to raise a TypeError as it does >> now? >> > > It works for me if I don't use the keyword.  That is, > >  >>>

Re: [Numpy-discussion] Solving a NLLSQ Problem by Pieces?

Found hugin (google), but I think it's a bit too general for my current interests. You might enjoy an optimization video course from Stanford Univ on the web. -- Wayne Watson (Watson Adventures

Re: [Numpy-discussion] Solving a NLLSQ Problem by Pieces?

Thanks for the info. Where do I find hugin? The paper I'm looking is from 1987. It is not clear what actual method he used. Probably something popular of those times. Things have changed. :-) Yes, scipy might be a better place to post this, and I will. Hmmm, I think I have had problems finding

[Numpy-discussion] Is numpy ignoring CFLAGS?

On some 64-bit platforms, which include, but is not limited to: * Some version of OS X (I don't know what versions or processors) * Solaris on SPARC processors. * Solaris on x86 processors. * OpenSolaris on SPARC processors. * OpenSolaris on x86 processors. * HP-UX on PA-RISC processor

[Numpy-discussion] issue #1431 accessing multiple fields in a recarray

Hello A while ago there was a discussion about field order when accessing recarrays. eg: >>> x = np.array([(1.5,2.5,(1.0,2.0)),(3.,4.,(4.,5.)),(1.,3.,(2.,6.))], dtype=[('x','f4'),('y',np.float32),('value','f4',(2,2))]) >>> x[['x','y']] array([(1.5, 2.5), (3.0, 4.0), (1.0, 3.0)], d

Re: [Numpy-discussion] numpy.random.poisson docs missing "Returns"

Sat, 26 Jun 2010 17:37:22 -0700, David Goldsmith wrote: > On Sat, Jun 26, 2010 at 3:22 PM, wrote: [clip] >> Is there a chance that some changes got lost? > > (Almost) anything's possible... :-( There's practically no change of edits getting lost. There's a change of them being hidden if things a