Re: [Numpy-discussion] What should be the result in some statistics corner cases?

On Mon, Jul 15, 2013 at 8:34 AM, Sebastian Berg wrote: > On Mon, 2013-07-15 at 07:52 -0600, Charles R Harris wrote: > > > > > > On Sun, Jul 14, 2013 at 3:35 PM, Charles R Harris > > wrote: > > > > > > > > >

Re: [Numpy-discussion] What should be the result in some statistics corner cases?

On Mon, Jul 15, 2013 at 8:34 AM, Sebastian Berg wrote: > On Mon, 2013-07-15 at 07:52 -0600, Charles R Harris wrote: > > > > > > On Sun, Jul 14, 2013 at 3:35 PM, Charles R Harris > > wrote: > > > > > > > > >

Re: [Numpy-discussion] What should be the result in some statistics corner cases?

On Mon, Jul 15, 2013 at 8:25 AM, Benjamin Root wrote: > This is going to need to be heavily documented with doctests. Also, just > to clarify, are we talking about a ValueError for doing a nansum on an > empty array as well, or will that now return a zero? > > I was going to leave nansum as is, a

Re: [Numpy-discussion] What should be the result in some statistics corner cases?

On Sun, Jul 14, 2013 at 3:35 PM, Charles R Harris wrote: > > > On Sun, Jul 14, 2013 at 2:55 PM, Warren Weckesser < > warren.weckes...@gmail.com> wrote: > >> On 7/14/13, Charles R Harris wrote: >> > Some corner cases in the mean, var, std. >> > >

Re: [Numpy-discussion] What should be the result in some statistics corner cases?

On Sun, Jul 14, 2013 at 2:55 PM, Warren Weckesser < warren.weckes...@gmail.com> wrote: > On 7/14/13, Charles R Harris wrote: > > Some corner cases in the mean, var, std. > > > > *Empty arrays* > > > > I think these cases should either raise an erro

[Numpy-discussion] What should be the result in some statistics corner cases?

Some corner cases in the mean, var, std. *Empty arrays* I think these cases should either raise an error or just return nan. Warnings seem ineffective to me as they are only issued once by default. In [3]: ones(0).mean() /home/charris/.local/lib/python2.7/site-packages/numpy/core/_methods.py:61:

[Numpy-discussion] nansum, nanmean, nanvar, nanstd

Hi All, I've been working on Benjamin's PR, which I took down as he didn't have time to finish it. I've made the following changes and thought I'd run them past others before putting up a new pull request. 1. The new functions are consolidated with the old ones inn (new) numpy/lib/nanfunct

Re: [Numpy-discussion] numpy.sign query

On Fri, Jul 12, 2013 at 12:53 PM, Alan G Isaac wrote: > The docs for numpy.sign at > http://docs.scipy.org/doc/numpy/reference/generated/numpy.sign.html > do not indicate how complex numbers are handled. Currently, np.sign > appears to return the sign of the real part as a complex value. > Was t

Re: [Numpy-discussion] add .H attribute?

On Sun, Jul 7, 2013 at 9:28 AM, Alan G Isaac wrote: > With numpy arrays, I miss being able to spell a.conj().T as a.H, > as one can with numpy matrices. > > Is adding this attribute to arrays ever under consideration? > There was a long thread about this back around 1.1 or so, long time ago in a

Re: [Numpy-discussion] numpy.filled, again

On Sat, Jun 29, 2013 at 7:15 PM, wrote: > On Sat, Jun 29, 2013 at 3:00 PM, Ralf Gommers > wrote: > > > > > > > > On Sat, Jun 29, 2013 at 6:43 PM, wrote: > >> > >> On Sat, Jun 29, 2013 at 12:04 PM, Charles R Harris > >> wrote: > &

Re: [Numpy-discussion] numpy.filled, again

On Sat, Jun 29, 2013 at 4:37 AM, Nathaniel Smith wrote: > So this petered off...any objections to np.full? > How about `np.inited` ? `full` doesn't sound quite right to me. Although I expect once it comes into use everyone will get used to it. Chuck __

Re: [Numpy-discussion] Automatic custom dtype

On Fri, Jun 28, 2013 at 5:27 AM, Richard Hattersley wrote: > On 21 June 2013 19:57, Charles R Harris wrote: > > You could check the numpy/core/src/umath/test_rational.c.src code to see > if > > you are missing something. > > In v1.7+ the difference in behaviour between

Re: [Numpy-discussion] Automatic custom dtype

On Fri, Jun 28, 2013 at 5:27 AM, Richard Hattersley wrote: > On 21 June 2013 19:57, Charles R Harris wrote: > > You could check the numpy/core/src/umath/test_rational.c.src code to see > if > > you are missing something. > > In v1.7+ the difference in behaviour between

Re: [Numpy-discussion] Automatic custom dtype

On Fri, Jun 21, 2013 at 12:53 PM, Charles R Harris < charlesr.har...@gmail.com> wrote: > > > On Fri, Jun 21, 2013 at 9:18 AM, Richard Hattersley > wrote: > >> On 21 June 2013 14:49, Charles R Harris >> wrote: >> > Bit short on detail here ;) How di

Re: [Numpy-discussion] Automatic custom dtype

On Fri, Jun 21, 2013 at 9:18 AM, Richard Hattersley wrote: > On 21 June 2013 14:49, Charles R Harris wrote: > > Bit short on detail here ;) How did you create/register the dtype? > > The dtype is created/registered during module initialisation with: > dtype = PyObject

Re: [Numpy-discussion] Automatic custom dtype

On Fri, Jun 21, 2013 at 7:09 AM, Richard Hattersley wrote: > Hi all, > > In my continuing adventures in the Land of Custom Dtypes I've come > across some rather disappointing behaviour in 1.7 & 1.8. > > I've defined my own class `Time360`, and a corresponding dtype > `time360` which references Tim

Re: [Numpy-discussion] low level optimization in NumPy and minivect

On Wed, Jun 19, 2013 at 5:45 AM, Matthew Brett wrote: > Hi, > > On Wed, Jun 19, 2013 at 1:43 AM, Frédéric Bastien wrote: > > Hi, > > > > > > On Mon, Jun 17, 2013 at 5:03 PM, Julian Taylor > > wrote: > >> > >> On 17.06.2013 17:11, Frédéric Bastien wrote: > >> > Hi, > >> > > >> > I saw that recent

Re: [Numpy-discussion] Profiling (was GSoC : Performance parity between numpy arrays and Python scalars)

On Mon, Jun 17, 2013 at 9:29 AM, Arink Verma wrote: > Hi Nathaniel > > It's a probabilistic sampling profiler, so if it doesn't have enough >> samples then it can miss things. 227 samples is way way too low. You need >> to run the profiled code for longer (a few seconds at least), and if that's >

Re: [Numpy-discussion] please close 611, 629, 2490, 2264

On Sun, Jun 16, 2013 at 6:40 PM, Eric Firing wrote: > Github issues 611, 629, and 2490 are duplicates. 611 included patches > with a test and a fix, both of which were committed long ago, so all > three issues should be closed. > > Please see my comment on 2264 as to why that should be closed. >

Re: [Numpy-discussion] Seg. fault when running tests

On Sat, Jun 15, 2013 at 2:26 PM, Charles R Harris wrote: > > > On Sat, Jun 15, 2013 at 2:23 PM, Warren Weckesser < > warren.weckes...@gmail.com> wrote: > >> >> On Sat, Jun 15, 2013 at 4:03 PM, Julian Taylor < >> jtaylor.deb...@googlemail.com> wrote:

Re: [Numpy-discussion] Seg. fault when running tests

On Sat, Jun 15, 2013 at 2:23 PM, Warren Weckesser < warren.weckes...@gmail.com> wrote: > > On Sat, Jun 15, 2013 at 4:03 PM, Julian Taylor < > jtaylor.deb...@googlemail.com> wrote: > >> On 15.06.2013 21:57, Warren Weckesser wrote: >> > >> > On Sat, Jun 15, 2013 at 3:15 PM, Julian Taylor >> >> >

Re: [Numpy-discussion] Seg. fault when running tests

aylor.deb...@googlemail.com> wrote: >> >>> On 15.06.2013 21:12, Charles R Harris wrote: >>> > >>> > >>> > On Sat, Jun 15, 2013 at 9:50 AM, Warren Weckesser >>> > mailto:warren.weckes...@gmail.com>> >>> wrote: &g

Re: [Numpy-discussion] Seg. fault when running tests

On Sat, Jun 15, 2013 at 1:15 PM, Julian Taylor < jtaylor.deb...@googlemail.com> wrote: > On 15.06.2013 21:12, Charles R Harris wrote: > > > > > > On Sat, Jun 15, 2013 at 9:50 AM, Warren Weckesser > > mailto:warren.weckes...@gmail.com>> wrote: > >

Re: [Numpy-discussion] Seg. fault when running tests

On Sat, Jun 15, 2013 at 9:50 AM, Warren Weckesser < warren.weckes...@gmail.com> wrote: > > On Sat, Jun 15, 2013 at 11:43 AM, Warren Weckesser < > warren.weckes...@gmail.com> wrote: > >> I'm getting a seg. fault in master when I run the tests. I'm on Ubuntu >> 12.04 64 bit, with Python 3.3.2 (64 b

Re: [Numpy-discussion] Not checking github

On Sat, Jun 15, 2013 at 4:00 AM, Sebastian Berg wrote: > Just to note, I disabled most github notifications for time reasons for > the next months, so if something pops up that you think I should look > at, use @mention. > OK. Thanks for the work you have done. We'll look for your return. Chuck

Re: [Numpy-discussion] Generating special polynomials (Chebyshev, Hermite etc.)

On Fri, Jun 14, 2013 at 6:59 PM, Kumar Appaiah wrote: > Dear Numpy Users, > > I am trying to find out a way by which I can easily generate the n-th > order "special" polynomial, where "special" could refer to Hermite, > Chebyshev etc. Numpy 1.7 introduces several methods for such > polynomials, bu

Re: [Numpy-discussion] Memory leak

On Thu, Jun 13, 2013 at 8:56 AM, Aron Ahmadia wrote: > Hi Petro, > > What version of numpy are you running? > > A > > > On Thu, Jun 13, 2013 at 3:50 PM, Pietro Bonfa' > wrote: > >> Dear Numpy users, >> >> I have a memory leak in my code. A simple way to reproduce my problem is: >> >> import nump

Re: [Numpy-discussion] suggested change of behavior for interp

On Wed, Jun 5, 2013 at 12:00 PM, Charles R Harris wrote: > > > On Wed, Jun 5, 2013 at 11:59 AM, Charles R Harris < > charlesr.har...@gmail.com> wrote: > >> >> >> On Wed, Jun 5, 2013 at 11:48 AM, Nathaniel Smith wrote: >> >>> On Wed, Jun

Re: [Numpy-discussion] suggested change of behavior for interp

On Wed, Jun 5, 2013 at 11:59 AM, Charles R Harris wrote: > > > On Wed, Jun 5, 2013 at 11:48 AM, Nathaniel Smith wrote: > >> On Wed, Jun 5, 2013 at 6:08 PM, Julian Taylor >> wrote: >> > On 05.06.2013 16:33, Nathaniel Smith wrote: >> >> The slow down

Re: [Numpy-discussion] suggested change of behavior for interp

On Wed, Jun 5, 2013 at 11:48 AM, Nathaniel Smith wrote: > On Wed, Jun 5, 2013 at 6:08 PM, Julian Taylor > wrote: > > On 05.06.2013 16:33, Nathaniel Smith wrote: > >> The slow down people are worried about is, suppose that 'xp' has > >> 1,000,000 entries, and the user wants to interpolate 1 point

Re: [Numpy-discussion] supporting quad precision

Hi Anne, Long time no see ;) On Wed, Jun 5, 2013 at 10:07 AM, Anne Archibald wrote: > Hi folks, > > I recently came across an application I needed quad precision for > (high-accuracy solution of a differential equation). I found a C++ library > (odeint) that worked for the integration itself, b

Re: [Numpy-discussion] suggested change of behavior for interp

On Tue, Jun 4, 2013 at 12:07 PM, Slavin, Jonathan wrote: > Hi, > > I would like to suggest that the behavior of numpy.interp be changed > regarding treatment of situations in which the x-coordinates are not > monotonically increasing. Specifically, it seems to me that interp should > work correct

Re: [Numpy-discussion] numpy tests errors and failures

On Sat, Jun 1, 2013 at 4:50 PM, Warren Weckesser wrote: > I'm getting a failure and two errors with the latest master branch: > > $ python -c "import numpy; numpy.test('full')" > Running unit tests for numpy > NumPy version 1.8.0.dev-dff8c94 > NumPy is installed in > /home/warren/local_numpy/lib/

[Numpy-discussion] 1.8 release update

Hi All, Most of the PR's that were mentioned as desirable for the 1.8 release have been merged, or look to be merged in the next week or two. The current list of blockersdoesn't look to severe to me but I suspect that it is inco

[Numpy-discussion] quickselect

Hi All, There is a PR adding quickselect to numpy as a function `partition`. Comments on name and exposure in the numpy API are welcome. Chuck ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http:/

Re: [Numpy-discussion] multivariate_normal issue with 'size' argument

On Fri, May 24, 2013 at 1:09 PM, Christoph Gohlke wrote: > This patch works for me: > > diff --git a/numpy/random/mtrand/mtrand.pyx > b/numpy/random/mtrand/mtrand.pyx > index b0de560..233ff52 100644 > --- a/numpy/random/mtrand/mtrand.pyx > +++ b/numpy/random/mtrand/mtrand.pyx > @@ -4156,7 +4156

Re: [Numpy-discussion] NumPy sprints at Scipy 2013, Austin: call for topics and hands to help

On Sat, May 25, 2013 at 6:59 PM, Benjamin Root wrote: > > On Sat, May 25, 2013 at 12:37 PM, Charles R Harris < > charlesr.har...@gmail.com> wrote: > >> >> >> On Sat, May 25, 2013 at 9:51 AM, David Cournapeau wrote: >> >>> On Sat, M

Re: [Numpy-discussion] NumPy sprints at Scipy 2013, Austin: call for topics and hands to help

On Sat, May 25, 2013 at 9:51 AM, David Cournapeau wrote: > On Sat, May 25, 2013 at 4:19 PM, Charles R Harris > wrote: > > > > > > On Sat, May 25, 2013 at 8:23 AM, David Cournapeau > > wrote: > >> > >> Hi there, > >> > >&g

Re: [Numpy-discussion] NumPy sprints at Scipy 2013, Austin: call for topics and hands to help

On Sat, May 25, 2013 at 8:23 AM, David Cournapeau wrote: > Hi there, > > I agreed to help organising NumPy sprints during the scipy 2013 > conference in Austin. > > As some of you may know, Stéfan and me will present a tutorial on > NumPy C code, so if we do our job correctly, we should have a few

[Numpy-discussion] stdint.h

Hi all, Just seeking some info here. The file stdint.h was part of the C99 standard and has types for integers of specified width and thus could be used to simplify some of the numpy configuration. I'm curious as to which compilers might be a problem and what folks think of that possibility. Chuc

Re: [Numpy-discussion] Integer overflow in test_einsum (1.7.1)

On Tue, May 14, 2013 at 11:26 AM, Toder, Evgeny wrote: > Hello, > > ** ** > > One of the test cases in test_einsum causes integer overflow for i2 type. > The test goes like this: > > ** ** > > >>> import numpy as np > > >>> dtype = 'i2' > > >>> n = 15 > > >>> a = np.arange(4*n

Re: [Numpy-discussion] __array_priority__ don't work for gt, lt, ... operator

On Fri, May 10, 2013 at 10:08 AM, Frédéric Bastien wrote: > Hi, > > it popped again on the Theano mailing list that this don't work: > > np.arange(10) <= a_theano_vector. > > The reason is that __array_priority__ isn't respected for that class of > operation. > > This page explain the problem and

Re: [Numpy-discussion] mpfr integration into numpy?

On Mon, May 6, 2013 at 7:57 AM, Nathaniel Smith wrote: > On Mon, May 6, 2013 at 8:52 AM, Funky Dev wrote: > > Hi, > > > > I've got a project in which it turns out we need much higher precision > > than even __float128 and playing around with a few alternatives mpfr > > seems to be the highest pe

Re: [Numpy-discussion] GSoC : Performance parity between numpy arrays and Python scalars

On Fri, May 3, 2013 at 12:13 PM, Arink Verma wrote: > I have created a new PR, have removed one irrelevant version check. > https://github.com/numpy/numpy/pull/3304/files > I made some remarks on the PR. The convention on numpy-discussion is bottom posting so you should do that to avoid future c

Re: [Numpy-discussion] GSoC : Performance parity between numpy arrays and Python scalars

On Thu, May 2, 2013 at 6:47 PM, wrote: > On Thu, May 2, 2013 at 6:30 PM, Ralf Gommers > wrote: > > > > > > > > On Fri, May 3, 2013 at 12:29 AM, Ralf Gommers > > wrote: > >> > >> > >> > >> > >> On Thu, May 2, 201

Re: [Numpy-discussion] GSoC : Performance parity between numpy arrays and Python scalars

On Thu, May 2, 2013 at 11:49 AM, Ralf Gommers wrote: > > > > On Thu, May 2, 2013 at 6:45 PM, Pauli Virtanen wrote: > >> Charles R Harris gmail.com> writes: >> [clip] >> > * Did you notice this line on the requirements page? "Having your >> >

Re: [Numpy-discussion] GSoC : Performance parity between numpy arrays and Python scalars

On Thu, May 2, 2013 at 7:14 AM, Nathaniel Smith wrote: > On Thu, May 2, 2013 at 6:26 AM, Arink Verma > wrote: > > Yes, we need to ensure that.. > > Code generator can be made, which can create code for table of registered > > dtype during build time itself. > > I'd probably just generate it at r

Re: [Numpy-discussion] nanmean(), nanstd() and other "missing" functions for 1.8

On Thu, May 2, 2013 at 8:40 AM, Robert Kern wrote: > On Thu, May 2, 2013 at 3:28 PM, Charles R Harris > wrote: > > > > > > On Thu, May 2, 2013 at 7:47 AM, Robert Kern > wrote: > >> > >> On Thu, May 2, 2013 at 2:38 PM, Charles R Harris > >>

Re: [Numpy-discussion] nanmean(), nanstd() and other "missing" functions for 1.8

On Thu, May 2, 2013 at 7:47 AM, Robert Kern wrote: > On Thu, May 2, 2013 at 2:38 PM, Charles R Harris > wrote: > > > > On Thu, May 2, 2013 at 7:28 AM, Robert Kern > wrote: > >> > >> On Thu, May 2, 2013 at 12:03 PM, Nathaniel Smith wrote: > &

Re: [Numpy-discussion] nanmean(), nanstd() and other "missing" functions for 1.8

On Thu, May 2, 2013 at 7:28 AM, Robert Kern wrote: > On Thu, May 2, 2013 at 12:03 PM, Nathaniel Smith wrote: > > On 1 May 2013 23:12, "Charles R Harris" > wrote: > >> > >> On Wed, May 1, 2013 at 7:10 PM, Benjamin Root wrote: > &

Re: [Numpy-discussion] GSoC : Performance parity between numpy arrays and Python scalars

On Tue, Apr 30, 2013 at 8:26 PM, Arink Verma wrote: > Hi all! > I have written my application[1] for *Performance parity between numpy > arrays and Python scalars[2]. *It would be a great help if you view it. > Does it look achievable and deliverable according to the project. > > [1] > http://www.

Re: [Numpy-discussion] nanmean(), nanstd() and other "missing" functions for 1.8

On Wed, May 1, 2013 at 7:10 PM, Benjamin Root wrote: > So, to summarize the thread so far: > > Consensus: > np.nanmean() > np.nanstd() > np.minmax() > np.argminmax() > > Vague Consensus: > np.sincos() > > If the return of sincos (cossin?) is an array, then it could be reshaped to be exp(1j*x), wh

Re: [Numpy-discussion] GSoC proposal -- Numpy SciPy

On Tue, Apr 30, 2013 at 1:37 PM, Nathaniel Smith wrote: > On Tue, Apr 30, 2013 at 3:19 PM, Blake Griffith > wrote: > > Hello, I'm writing a GSoC proposal, mostly concerning SciPy, but it > involves > > a few changes to NumPy. > > The proposal is titled: Improvements to the sparse package of Scip

Re: [Numpy-discussion] 1.8 release

On Mon, Apr 29, 2013 at 1:04 PM, Benjamin Root wrote: > > On Thu, Apr 25, 2013 at 11:16 AM, Charles R Harris < > charlesr.har...@gmail.com> wrote: > >> Hi All, >> >> I think it is time to start the runup to the 1.8 release. I don't know of >> any ou

Re: [Numpy-discussion] 1.8 release

On Mon, Apr 29, 2013 at 12:58 PM, Chris Barker - NOAA Federal < chris.bar...@noaa.gov> wrote: > On Thu, Apr 25, 2013 at 8:19 AM, Dave Hirschfeld < > dave.hirschf...@gmail.com> wrote: > >> > Hi All,I think it is time to start the runup to the 1.8 release. I don't >> know of any outstanding blockers

Re: [Numpy-discussion] Proposal of new function: iteraxis()

On Thu, Apr 25, 2013 at 1:51 PM, wrote: > On Thu, Apr 25, 2013 at 3:40 PM, Robert Kern > wrote: > > On Thu, Apr 25, 2013 at 8:21 PM, Andrew Giessel > > wrote: > >> I respect this opinion. However (and maybe this is legacy), while > reading > >> through the numeric.py source file, I was surpris

[Numpy-discussion] 1.8 release

Hi All, I think it is time to start the runup to the 1.8 release. I don't know of any outstanding blockers but if anyone has a PR/issue that they feel needs to be in the next Numpy release now is the time to make it known. Chuck ___ NumPy-Discussion mai

Re: [Numpy-discussion] MapIter api

On Tue, Apr 23, 2013 at 4:06 PM, Sebastian Berg wrote: > On Tue, 2013-04-23 at 17:08 -0400, Frédéric Bastien wrote: > > Hi, > > > > this is currently used in Theano! In fact, it is a John S. that > > implemented it in NumPy to allow fast gradient of the advanced > > indexing in Theano. It allow co

Re: [Numpy-discussion] KeepDims flag?

On Sun, Apr 21, 2013 at 4:59 AM, Sebastian Berg wrote: > Hi, > > just something that has been spooking around in my mind. Considering > that matrix indexing does not really support fancy indexing, I was > wondering about introducing a KeepDims flag. Maybe it is not worth it, > at least not unless

Re: [Numpy-discussion] contributing to numpy

On Wed, Apr 17, 2013 at 6:29 AM, andrew giessel wrote: > First, my apologies if this isn't the right forum for this question- I > looked for a dev list, but couldn't really find it. > > I have a small method I'd like to contribute to numpy, ideally as a method > on ndarrays and a general function

Re: [Numpy-discussion] datetime64 1970 issue

On Tue, Apr 16, 2013 at 6:45 PM, Benjamin Root wrote: > > On Tue, Apr 16, 2013 at 7:45 PM, Ondřej Čertík wrote: > >> On Tue, Apr 16, 2013 at 4:55 PM, Bob Nnamtrop >> wrote: >> > I am curious if others have noticed an issue with datetime64 at the >> > beginning of 1970. First: >> > >> > In [144]:

Re: [Numpy-discussion] MapIter api

On Mon, Apr 15, 2013 at 1:27 PM, Sebastian Berg wrote: > On Mon, 2013-04-15 at 11:16 -0600, Charles R Harris wrote: > > > > > > On Mon, Apr 15, 2013 at 10:29 AM, Sebastian Berg > > wrote: > > Hey, > > > > the MapIter API

Re: [Numpy-discussion] MapIter api

On Mon, Apr 15, 2013 at 10:29 AM, Sebastian Berg wrote: > Hey, > > the MapIter API has only been made public in master right? So it is no > problem at all to change at least the mapiter struct, right? > > I got annoyed at all those special cases that make things difficult to > get an idea where t

[Numpy-discussion] Adding gufuncs

There is a pull request for work adding linear algebra support as generalized ufuncs. The result is that many of the linear algebra routines can now be applied to stacks of matrices. Another new feature is support for float32 versions of the routines. Some

Re: [Numpy-discussion] Please stop bottom posting!!

On Thu, Apr 11, 2013 at 5:49 PM, Colin J. Williams wrote: > On 11/04/2013 7:20 PM, Paul Hobson wrote: > > On Wed, Apr 3, 2013 at 4:28 PM, Doug Coleman wrote: > >> >> Also, gmail "bottom-posts" by default. It's transparent to gmail users. >> I'd imagine they are some of the biggest offenders. >>

Re: [Numpy-discussion] Scheduling the 1.7.1 and 1.8 releases

On Thu, Apr 11, 2013 at 10:12 AM, Nathaniel Smith wrote: > On 11 Apr 2013 15:29, "Charles R Harris" > wrote: > > > > > > > > On Thu, Apr 11, 2013 at 4:32 AM, Sebastian Berg < > sebast...@sipsolutions.net> wrote: > >> > >> On We

Re: [Numpy-discussion] Scheduling the 1.7.1 and 1.8 releases

On Thu, Apr 11, 2013 at 4:32 AM, Sebastian Berg wrote: > On Wed, 2013-03-06 at 11:43 -0700, Charles R Harris wrote: > > Hi All, > > > > > > The development branch has been accumulating stuff since last summer, > > I suggest we look to get it out in May, branc

Re: [Numpy-discussion] Numpy discussion - was: Raveling, reshape order keyword unnecessarily confuses index and memory ordering

On Mon, Apr 8, 2013 at 5:30 PM, Paul Ivanov wrote: > Ralf Gommers, on 2013-04-09 00:06, wrote: > > G. website improvement --> thank you, desperately needed. Here's some > login > > credentials and a medal. > > see https://github.com/numpy/numpy.org/pull/1 > > Do I really get a medal? ;) > Send

Re: [Numpy-discussion] Sort performance with structured array

On Sun, Apr 7, 2013 at 5:56 PM, Charles R Harris wrote: > > > On Sun, Apr 7, 2013 at 5:23 PM, Tom Aldcroft < > aldcr...@head.cfa.harvard.edu> wrote: > >> I'm seeing about a factor of 50 difference in performance between >> sorting a random integer array versu

Re: [Numpy-discussion] Sort performance with structured array

On Sun, Apr 7, 2013 at 5:23 PM, Tom Aldcroft wrote: > I'm seeing about a factor of 50 difference in performance between > sorting a random integer array versus sorting that same array viewed > as a structured array. Am I doing anything wrong here? > > In [2]: x = np.random.randint(1, size=100

Re: [Numpy-discussion] timezones and datetime64

On Thu, Apr 4, 2013 at 11:01 AM, Chris Barker - NOAA Federal < chris.bar...@noaa.gov> wrote: > On Wed, Apr 3, 2013 at 6:02 PM, Mark Wiebe wrote: > > On Wed, Apr 3, 2013 at 4:27 PM, Pauli Virtanen wrote: > > >> Probably also TAI and UTC/Posix. > >> > >> Converting from one format to the other is

[Numpy-discussion] Moving linalg c code

Hi All, There is a PR that adds some blas and lapack functions to numpy. I'm thinking that if that PR is merged it would be good to move all of the blas and lapack functions, including the current ones in numpy/linalg into a single directory somewhere in

Re: [Numpy-discussion] try to solve issue #2649 and revisit #473

On Wed, Apr 3, 2013 at 5:11 PM, huangkan...@gmail.com wrote: > Agree with the row-vector and column-vector thing. I notice that in > ndarray multiplication, the 1-d array is treated as a column-vector. But > in matrix multiplication, 1-d array is converted to a row-vector. So just > match the 1-d

Re: [Numpy-discussion] Please stop bottom posting!!

What's the problem? ;) Chuck ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion

[Numpy-discussion] Sphinx question

Making the numpy documentation generates hundreds of warnings like ...doc/source/reference/generated/numpy.memmap.argsort.rst:: WARNING: document isn't included in any toctree Note that argsort is a method inherited from ndarray. These warnings are repeated for all ndarray methods in all classes

Re: [Numpy-discussion] ANN: NumPy 1.7.1rc1 release

On Sun, Mar 24, 2013 at 3:02 PM, Ondřej Čertík wrote: > Hi, > > I'm pleased to announce the availability of the first release candidate of > NumPy 1.7.1rc1. > > Sources and binary installers can be found at > https://sourceforge.net/projects/numpy/files/NumPy/1.7.1rc1/ > > Please test it and repor

[Numpy-discussion] Numpy 1.7.1

The Numpy 1.7.1 release process seems to have stalled. What do we need to finish up to get it going again? I think it would be nice to shoot for a release maybe the weekend after next. Chuck ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org ht

[Numpy-discussion] Videos of PyCon talks.

Here . Chuck ___ NumPy-Discussion mailing list NumPy-Discussion@scipy.org http://mail.scipy.org/mailman/listinfo/numpy-discussion

Re: [Numpy-discussion] R: fast numpy.fromfile skipping data chunks

On Wed, Mar 13, 2013 at 9:54 AM, Andrea Cimatoribus < andrea.cimatori...@nioz.nl> wrote: > Thanks a lot for the feedback, I'll try to modify my function to overcome > this issue. > Since I'm in the process of buying new hardware too, a slight OT (but > definitely related). > Does an ssd provide su

Re: [Numpy-discussion] polyfit with fixed points

On Thu, Mar 7, 2013 at 9:22 AM, eat wrote: > Hi, > > On Thu, Mar 7, 2013 at 1:52 AM, Jaime Fernández del Río < > jaime.f...@gmail.com> wrote: > >> On Tue, Mar 5, 2013 at 5:23 AM, Charles R Harris < >> charlesr.har...@gmail.com> wrote: >> >&

Re: [Numpy-discussion] polyfit with fixed points

On Wed, Mar 6, 2013 at 4:52 PM, Jaime Fernández del Río < jaime.f...@gmail.com> wrote: > On Tue, Mar 5, 2013 at 5:23 AM, Charles R Harris < > charlesr.har...@gmail.com> wrote: > >> >> >> On Tue, Mar 5, 2013 at 12:41 AM, Jaime Fernández del Río < >>

[Numpy-discussion] Scheduling the 1.7.1 and 1.8 releases

Hi All, There are now some 14 non-merge commits in the 1.7.x branch including the critical diagonal leak fix. I think there is maybe one more critical backport and perhaps several low priority fixes, documentation and such, but I think we should start up the release process with a goal of getting

Re: [Numpy-discussion] polyfit with fixed points

On Tue, Mar 5, 2013 at 6:23 AM, Charles R Harris wrote: > > > On Tue, Mar 5, 2013 at 12:41 AM, Jaime Fernández del Río < > jaime.f...@gmail.com> wrote: > >> On Mon, Mar 4, 2013 at 8:37 PM, Charles R Harris < >> charlesr.har...@gmail.com> wrote: >>

Re: [Numpy-discussion] polyfit with fixed points

On Tue, Mar 5, 2013 at 12:41 AM, Jaime Fernández del Río < jaime.f...@gmail.com> wrote: > On Mon, Mar 4, 2013 at 8:37 PM, Charles R Harris < > charlesr.har...@gmail.com> wrote: > >> >> There are actually seven versions of polynomial fit, two for the usual >

Re: [Numpy-discussion] Remove interactive setup

gt;> remove it. >> >> A >> >> >> On Mon, Mar 4, 2013 at 11:10 PM, Charles R Harris < >> charlesr.har...@gmail.com> wrote: >> >>> In distutils there are three files that provide some interactive setup: >>> >>> >

Re: [Numpy-discussion] polyfit with fixed points

On Mon, Mar 4, 2013 at 5:23 PM, Jaime Fernández del Río < jaime.f...@gmail.com> wrote: > A couple of days back, answering a question in StackExchange ( > http://stackoverflow.com/a/15196628/110026), I found myself using > Lagrange multipliers to fit a polynomial with least squares to data, making

Re: [Numpy-discussion] polyfit with fixed points

On Mon, Mar 4, 2013 at 5:53 PM, Aron Ahmadia wrote: > Interesting, that question would probably have gotten a different response > on scicomp, it is a pity we are not attracting more questions there! > > I know there are two polyfit modules in numpy, one in numpy.polyfit, the > other in numpy.pol

[Numpy-discussion] Remove interactive setup

In distutils there are three files that provide some interactive setup: 1. numpy/distutils/core.py 2. numpy/distutils/fcompiler/gnu.py 3. numpy/distutils/interactive.py In Python3 `raw_input` has been renamed 'input' and python2 'input' is gone. I propose that the easiest solution to th

Re: [Numpy-discussion] Plans for missing data

On Wed, Feb 27, 2013 at 8:31 AM, Lluís wrote: > Hi there, > > I haven't been able to find an answer after a quick search, but are there > any > plans regarding the (re)inclusion of missing data support into some future > version of numpy? > > Not at the moment, but it sits in the back of my mind.

Re: [Numpy-discussion] polyfit in NumPy v1.7

On Wed, Feb 27, 2013 at 6:46 AM, David Pine wrote: > As of NumPy v1.7, numpy.polyfit includes an option for providing weighting > to data to be fit. It's a welcome addition, but the implementation seems a > bit non-standard, perhaps even wrong, and I wonder if someone can enlighten > me. > > 1.

Re: [Numpy-discussion] 1.7.1

On Tue, Feb 26, 2013 at 5:43 PM, Ondřej Čertík wrote: > On Tue, Feb 26, 2013 at 1:21 PM, Charles R Harris > wrote: > > > > > > On Tue, Feb 26, 2013 at 2:03 PM, Ralf Gommers > > wrote: > >> > >> > >> > >> > >> On Tue, Feb

Re: [Numpy-discussion] 1.7.1

On Tue, Feb 26, 2013 at 2:46 PM, Nathaniel Smith wrote: > On Tue, Feb 26, 2013 at 9:21 PM, Charles R Harris > wrote: > > > > > > On Tue, Feb 26, 2013 at 2:03 PM, Ralf Gommers > > wrote: > >> > >> > >> > >> > >> On T

Re: [Numpy-discussion] 1.7.1

On Tue, Feb 26, 2013 at 2:03 PM, Ralf Gommers wrote: > > > > On Tue, Feb 26, 2013 at 7:47 PM, Charles R Harris < > charlesr.har...@gmail.com> wrote: > >> When should we put out 1.7.1? Discuss ;) >> > > When we have X times more fixes in maintenance/1.7.x

Re: [Numpy-discussion] Adding .abs() method to the array object

On Sat, Feb 23, 2013 at 1:33 PM, Robert Kern wrote: > On Sat, Feb 23, 2013 at 7:25 PM, Nathaniel Smith wrote: > > On Sat, Feb 23, 2013 at 3:38 PM, Till Stensitzki > wrote: > >> Hello, > >> i know that the array object is already crowded, but i would like > >> to see the abs method added, especi

Re: [Numpy-discussion] Adding .abs() method to the array object

On Mon, Feb 25, 2013 at 8:50 AM, Skipper Seabold wrote: > On Mon, Feb 25, 2013 at 10:43 AM, Till Stensitzki > wrote: > > > > First, sorry that i didnt search for an old thread, but because i > disagree with > > conclusion i would at least address my reason: > > > >> I don't like > >> np.abs(arr).

Re: [Numpy-discussion] Adding .abs() method to the array object

On Sat, Feb 23, 2013 at 12:25 PM, Nathaniel Smith wrote: > On Sat, Feb 23, 2013 at 3:38 PM, Till Stensitzki wrote: > > Hello, > > i know that the array object is already crowded, but i would like > > to see the abs method added, especially doing work on the console. > > Considering that many muc

Re: [Numpy-discussion] Windows, blas, atlas and dlls

On Mon, Feb 18, 2013 at 9:28 AM, Dag Sverre Seljebotn < d.s.seljeb...@astro.uio.no> wrote: > On 02/18/2013 05:26 PM, rif wrote: > > I have no answer to the question, but I was curious as to why directly > > calling the cblas would be 10x-20x slower in the first place. That > > seems surprising, a

Re: [Numpy-discussion] calling NumPy from Julia - a plea for fewer macros

On Sun, Feb 17, 2013 at 12:43 PM, Charles R Harris < charlesr.har...@gmail.com> wrote: > > > On Sun, Feb 17, 2013 at 9:12 AM, Steven G. Johnson > wrote: > >> Dear NumPy developers, >> >> I've been working on a glue package that allows the Julia langua

Re: [Numpy-discussion] calling NumPy from Julia - a plea for fewer macros

On Sun, Feb 17, 2013 at 9:12 AM, Steven G. Johnson wrote: > Dear NumPy developers, > > I've been working on a glue package that allows the Julia language > (http://julialang.org/) to call Python routines easily > https://github.com/stevengj/PyCall.jl > and I'm using NumPy to pass multidime

Re: [Numpy-discussion] Fwd: Package: scipy-0.11.0-0.1.rc2.fc18 Tag: f18-updates-candidate Status: failed Built by: orion

On Wed, Feb 13, 2013 at 5:18 PM, Ondřej Čertík wrote: > Orion, > > On Wed, Feb 13, 2013 at 4:06 PM, Orion Poplawski > wrote: > dsbevx_ Looks suspicious. There was a problem with 3.3and scipy in that function which should be fixed in the next release. S

<    4   5   6   7   8   9   10   11   12   13   >