Re: [Numpy-discussion] quantile() or percentile()

2017-07-21 Thread Chun-Wei Yuan
That would be great. I just used np.argsort because it was familiar to me. Didn't know about the C code. On Fri, Jul 21, 2017 at 3:43 PM, Joseph Fox-Rabinovitz < jfoxrabinov...@gmail.com> wrote: > While #9211 is a good start, it is pretty inefficient in terms of the fact > that it performs an O

Re: [Numpy-discussion] quantile() or percentile()

2017-07-21 Thread Joseph Fox-Rabinovitz
While #9211 is a good start, it is pretty inefficient in terms of the fact that it performs an O(nlogn) sort of the array. It is possible to reduce the time to O(n) by using a similar partitioning algorithm to the one in the C code of percentile. I will look into it as soon as I can. -Joe On

Re: [Numpy-discussion] quantile() or percentile()

2017-07-21 Thread Chun-Wei Yuan
Just to provide some context, 9213 actually spawned off of this guy: https://github.com/numpy/numpy/pull/9211 which might address the weighted inputs issue Joe brought up. C On Fri, Jul 21, 2017 at 2:21 PM, Joseph Fox-Rabinovitz < jfoxrabinov...@gmail.com> wrote: > I think that there would be

Re: [Numpy-discussion] quantile() or percentile()

2017-07-21 Thread Joseph Fox-Rabinovitz
I think that there would be a very good reason to have a separate function if we were to introduce weights to the inputs, similarly to the way that we have mean and average. This would have some (positive) repercussions like making weighted histograms with the Freedman-Diaconis binwidth estimator a

[Numpy-discussion] quantile() or percentile()

2017-07-21 Thread Chun-Wei Yuan
There's an ongoing effort to introduce quantile() into numpy. You'd use it just like percentile(), but would input your q value in probability space (0.5 for 50%): https://github.com/numpy/numpy/pull/9213 Since there's a great deal of overlap between these two functions, we'd like to solicit opi

Re: [Numpy-discussion] NumPy steering councils members

2017-07-21 Thread Sebastian Berg
On Fri, 2017-07-21 at 12:59 -0700, Nathaniel Smith wrote: > On Jul 21, 2017 9:36 AM, "Sebastian Berg" > wrote: > On Fri, 2017-07-21 at 16:58 +0200, Julian Taylor wrote: > > On 21.07.2017 08:52, Ralf Gommers wrote: > Also FWIW, the jupyter steering council is currently 15 people, or 16 > including

Re: [Numpy-discussion] NumPy steering councils members

2017-07-21 Thread Nathaniel Smith
On Jul 21, 2017 9:36 AM, "Sebastian Berg" wrote: On Fri, 2017-07-21 at 16:58 +0200, Julian Taylor wrote: > On 21.07.2017 08:52, Ralf Gommers wrote: > > Hi all, > > > > It has been well over a year since we put together the governance > > structure and steering council > > (https://docs.scipy.org/

Re: [Numpy-discussion] NumPy steering councils members

2017-07-21 Thread Sebastian Berg
On Fri, 2017-07-21 at 16:58 +0200, Julian Taylor wrote: > On 21.07.2017 08:52, Ralf Gommers wrote: > > Hi all, > > > > It has been well over a year since we put together the governance > > structure and steering council > > (https://docs.scipy.org/doc/numpy-dev/dev/governance/people.html#go > > ve

Re: [Numpy-discussion] NumPy steering councils members

2017-07-21 Thread Julian Taylor
On 21.07.2017 08:52, Ralf Gommers wrote: > Hi all, > > It has been well over a year since we put together the governance > structure and steering council > (https://docs.scipy.org/doc/numpy-dev/dev/governance/people.html#governance-people). > We haven't reviewed the people on the steering council

Re: [Numpy-discussion] NumPy steering councils members

2017-07-21 Thread Jaime Fernández del Río
On Fri, Jul 21, 2017 at 8:52 AM, Ralf Gommers wrote: > Hi all, > > It has been well over a year since we put together the governance > structure and steering council (https://docs.scipy.org/doc/ > numpy-dev/dev/governance/people.html#governance-people). We haven't > reviewed the people on the ste