Raul,
This is *fantastic work*. While many optimizations were done 6 years ago as
people started to convert their code, that kind of report has trailed off in
the last few years. I have not seen this kind of speed-comparison for some
time --- but I think it's definitely beneficial.
Num
On 12/2/2012 5:28 PM, Raul Cota wrote:
> Hello,
>
> First a quick summary of my problem and at the end I include the basic
> changes I am suggesting to the source (they may benefit others)
>
> I am ages behind in times and I am still using Numeric in Python 2.2.3.
> The main reason why it has taken
Hello,
First a quick summary of my problem and at the end I include the basic
changes I am suggesting to the source (they may benefit others)
I am ages behind in times and I am still using Numeric in Python 2.2.3.
The main reason why it has taken so long to upgrade is because NumPy
kills perfo
On Sun, Dec 2, 2012 at 3:16 PM, Ralf Gommers wrote:
>
> On Fri, Nov 30, 2012 at 9:07 AM, Martin Raspaud
> wrote:
>>
>> Hi,
>>
>> We noticed that comparing arrays of different shapes with allclose
>> doesn't work anymore in numpy 1.6.2.
>>
>> Is this a feature or a bug ? :)
>
>
> I vote for featur
On Fri, Nov 30, 2012 at 9:07 AM, Martin Raspaud wrote:
> Hi,
>
> We noticed that comparing arrays of different shapes with allclose
> doesn't work anymore in numpy 1.6.2.
>
> Is this a feature or a bug ? :)
>
I vote for feature. Allclose does element-wise comparison, so using
different size non-b
