Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Message from discussion New functions.
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Mark Miller  
View profile  
 More options Jun 1 2011, 11:31 am
From: Mark Miller <markperrymil...@gmail.com>
Date: Wed, 1 Jun 2011 08:31:55 -0700
Local: Wed, Jun 1 2011 11:31 am
Subject: Re: [Numpy-discussion] New functions.
I'd love to see something like a "count_unique" function included. The
numpy.unique function is handy, but it can be a little awkward to
efficiently go back and get counts of each unique value after the
fact.

-Mark

On Wed, Jun 1, 2011 at 8:17 AM, Keith Goodman <kwgood...@gmail.com> wrote:
> On Tue, May 31, 2011 at 8:41 PM, Charles R Harris
> <charlesr.har...@gmail.com> wrote:
>> On Tue, May 31, 2011 at 8:50 PM, Bruce Southey <bsout...@gmail.com> wrote:

>>> How about including all or some of Keith's Bottleneck package?
>>> He has tried to include some of the discussed functions and tried to
>>> make them very fast.

>> I don't think they are sufficiently general as they are limited to 2
>> dimensions. However, I think the moving filters should go into scipy, either
>> in ndimage or maybe signals. Some of the others we can still speed of
>> significantly, for instance nanmedian, by using the new functionality in
>> numpy, i.e., numpy sort has worked with nans for a while now. It looks like
>> call overhead dominates the nanmax times for small arrays and this might
>> improve if the ufunc machinery is cleaned up a bit more, I don't know how
>> far Mark got with that.

> Currently Bottleneck accelerates 1d, 2d, and 3d input. Anything else
> falls back to a slower, non-cython version of the function. The same
> goes for int32, int64, float32, float64.

> It should not be difficult to extend to higher nd and more dtypes
> since everything is generated from template. The problem is that there
> would be a LOT of cython auto-generated C code since there is a
> separate function for each ndim, dtype, axis combination.

> Each of the ndim, dtype, axis functions currently has its own copy of
> the algorithm (such as median). Pulling that out and reusing it should
> save a lot of trees by reducing the auto-generated C code size.

> I recently added a partsort and argpartsort.
> _______________________________________________
> NumPy-Discussion mailing list
> NumPy-Discuss...@scipy.org
> http://mail.scipy.org/mailman/listinfo/numpy-discussion

_______________________________________________
NumPy-Discussion mailing list
NumPy-Discuss...@scipy.org
http://mail.scipy.org/mailman/listinfo/numpy-discussion

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.