2012/7/31 eat :
> Hi,
>
> On Tue, Jul 31, 2012 at 7:20 PM, Vlastimil Brom
> wrote:
>>
>> 2012/7/31 eat :
>> > Hi,
>> >
>> > On Tue, Jul 31, 2012 at 5:01 PM, Vlastimil Brom
>> >
>> > wrote:
>> >>
>> >> 2012/7/31 eat :
>> >> > Hi,
>> >> >
>> >> > On Tue, Jul 31, 2012 at 10:23 AM, Vlastimil Brom
>>
Hi,
On Tue, Jul 31, 2012 at 7:20 PM, Vlastimil Brom wrote:
> 2012/7/31 eat :
> > Hi,
> >
> > On Tue, Jul 31, 2012 at 5:01 PM, Vlastimil Brom <
> vlastimil.b...@gmail.com>
> > wrote:
> >>
> >> 2012/7/31 eat :
> >> > Hi,
> >> >
> >> > On Tue, Jul 31, 2012 at 10:23 AM, Vlastimil Brom
> >> >
> >> >
Hi,
On Tue, Jul 31, 2012 at 7:30 PM, Nathaniel Smith wrote:
> On Tue, Jul 31, 2012 at 4:57 PM, eat wrote:
> > Hi,
> >
> > On Tue, Jul 31, 2012 at 6:43 PM, Nathaniel Smith wrote:
> >>
> >> On Tue, Jul 31, 2012 at 2:23 PM, eat wrote:
> >> > Apparently ast(.) does not return a view of the origin
On Tue, Jul 31, 2012 at 4:57 PM, eat wrote:
> Hi,
>
> On Tue, Jul 31, 2012 at 6:43 PM, Nathaniel Smith wrote:
>>
>> On Tue, Jul 31, 2012 at 2:23 PM, eat wrote:
>> > Apparently ast(.) does not return a view of the original matches rather
>> > a
>> > copy of size (n* (2* distance+ 1)), thus you ma
2012/7/31 eat :
> Hi,
>
> On Tue, Jul 31, 2012 at 5:01 PM, Vlastimil Brom
> wrote:
>>
>> 2012/7/31 eat :
>> > Hi,
>> >
>> > On Tue, Jul 31, 2012 at 10:23 AM, Vlastimil Brom
>> >
>> > wrote:
>> >>
>> >> 2012/7/30 eat :
>> >> > Hi,
>> >> >
>> >> > A partial answer to your questions:
>> >> >
>> >> >
Hi,
On Tue, Jul 31, 2012 at 6:43 PM, Nathaniel Smith wrote:
> On Tue, Jul 31, 2012 at 2:23 PM, eat wrote:
> > Apparently ast(.) does not return a view of the original matches rather a
> > copy of size (n* (2* distance+ 1)), thus you may run out of memory.
>
> The problem isn't memory, it's that
On Tue, Jul 31, 2012 at 2:23 PM, eat wrote:
> Apparently ast(.) does not return a view of the original matches rather a
> copy of size (n* (2* distance+ 1)), thus you may run out of memory.
The problem isn't memory, it's that on 32-bit Python,
np.prod(arr.shape) must be <2**32 (or maybe 2**31 --
Hi,
On Tue, Jul 31, 2012 at 5:01 PM, Vlastimil Brom wrote:
> 2012/7/31 eat :
> > Hi,
> >
> > On Tue, Jul 31, 2012 at 10:23 AM, Vlastimil Brom <
> vlastimil.b...@gmail.com>
> > wrote:
> >>
> >> 2012/7/30 eat :
> >> > Hi,
> >> >
> >> > A partial answer to your questions:
> >> >
> >> > On Mon, Jul 3
2012/7/31 eat :
> Hi,
>
> On Tue, Jul 31, 2012 at 10:23 AM, Vlastimil Brom
> wrote:
>>
>> 2012/7/30 eat :
>> > Hi,
>> >
>> > A partial answer to your questions:
>> >
>> > On Mon, Jul 30, 2012 at 10:33 PM, Vlastimil Brom
>> >
>> > wrote:
>> >>
>> >> Hi all,
>> >> I'd like to ask for some hints or
Hi,
On Tue, Jul 31, 2012 at 10:23 AM, Vlastimil Brom
wrote:
> 2012/7/30 eat :
> > Hi,
> >
> > A partial answer to your questions:
> >
> > On Mon, Jul 30, 2012 at 10:33 PM, Vlastimil Brom <
> vlastimil.b...@gmail.com>
> > wrote:
> >>
> >> Hi all,
> >> I'd like to ask for some hints or advice regar
2012/7/30 eat :
> Hi,
>
> A partial answer to your questions:
>
> On Mon, Jul 30, 2012 at 10:33 PM, Vlastimil Brom
> wrote:
>>
>> Hi all,
>> I'd like to ask for some hints or advice regarding the usage of
>> numpy.array and especially slicing.
>>
>> I only recently tried numpy and was impressed b
Hi,
A partial answer to your questions:
On Mon, Jul 30, 2012 at 10:33 PM, Vlastimil Brom
wrote:
> Hi all,
> I'd like to ask for some hints or advice regarding the usage of
> numpy.array and especially slicing.
>
> I only recently tried numpy and was impressed by the speedup in some
> parts of t
Hi all,
I'd like to ask for some hints or advice regarding the usage of
numpy.array and especially slicing.
I only recently tried numpy and was impressed by the speedup in some
parts of the code, hence I suspect, that I might miss some other
oportunities in this area.
I currently use the followi
13 matches
Mail list logo
