2009/4/29 Dan Goodman :
> Robert Kern wrote:
>> On Wed, Apr 29, 2009 at 16:19, Dan Goodman wrote:
>>> Robert Kern wrote:
On Wed, Apr 29, 2009 at 08:03, Daniel Yarlett
wrote:
> As you can see, Current is different in the two cases. Any ideas how I
> can recreate the behavio
Robert Kern wrote:
> On Wed, Apr 29, 2009 at 16:19, Dan Goodman wrote:
>> Robert Kern wrote:
>>> On Wed, Apr 29, 2009 at 08:03, Daniel Yarlett
>>> wrote:
>>>
As you can see, Current is different in the two cases. Any ideas how I
can recreate the behavior of the iterative process in a m
On Wed, Apr 29, 2009 at 16:19, Dan Goodman wrote:
> Robert Kern wrote:
>> On Wed, Apr 29, 2009 at 08:03, Daniel Yarlett
>> wrote:
>>
>>> As you can see, Current is different in the two cases. Any ideas how I
>>> can recreate the behavior of the iterative process in a more numpy-
>>> friendly, ve
Robert Kern wrote:
> On Wed, Apr 29, 2009 at 08:03, Daniel Yarlett
> wrote:
>
>> As you can see, Current is different in the two cases. Any ideas how I
>> can recreate the behavior of the iterative process in a more numpy-
>> friendly, vectorized (and hopefully quicker) way?
>
> Use bincount().
On Wed, Apr 29, 2009 at 08:03, Daniel Yarlett wrote:
> As you can see, Current is different in the two cases. Any ideas how I
> can recreate the behavior of the iterative process in a more numpy-
> friendly, vectorized (and hopefully quicker) way?
Use bincount().
> And possibly also
> about why
> As you can see, Current is different in the two cases. Any ideas how I
> can recreate the behavior of the iterative process in a more numpy-
> friendly, vectorized (and hopefully quicker) way? And possibly also
> about why my intuitions concerning the semantics of the vectorized
> code are
