Hi
I'm new to programming in python and I hope that this is the problem.
I've created a cellular automata program in python with the numpy array
extensions. After each cycle/iteration the memory used to examine and
change the array as determined by the transition rules is never freed.
I've tried
Serge Orlov wrote:
> sonjaa wrote:
> > Hi
> >
> > I'm new to programming in python and I hope that this is the problem.
> >
> > I've created a cellular automata program in python with the numpy array
> > extensions. After each cycle/iteration the m
Serge Orlov wrote:
> sonjaa wrote:
> > Serge Orlov wrote:
> > > sonjaa wrote:
> > > > Hi
> > > >
> > > > I'm new to programming in python and I hope that this is the problem.
> > > >
> > > > I've created a
Fredrik Lundh wrote:
> <[EMAIL PROTECTED]> wrote:
> > After doing this I see that iterative counters used to collect occurrences
> > and nested loop counters (ii & jj) as seen in the code example below
> > are the culprits with the worst ones over 1M:
> >
> > for ii in xrange(0,40)
Carl Banks wrote:
> sonjaa wrote:
> > I've created a cellular automata program in python with the numpy array
> > extensions. After each cycle/iteration the memory used to examine and
> > change the array as determined by the transition rules is never freed.
>
> A
on of the app, and the two associated
ascii files, if anyone is interested.
-Sonja
Fredrik Lundh wrote:
> sonjaa wrote:
>
> > "y" is a 500x500 array.
>
> a 500x500 array of what ? how did you create the array ?
>
>
--
http://mail.python.org/mailman/listinfo/python-list
Hi
last week I posted a problem with running out of memory when changing
values in NumPy arrays. Since then I have tried many different
approaches and
work-arounds but to no avail.
I was able to reduce the code (see below) to its smallest size and
still
have the problem, albeit at a slower rate.
I've been in contact with Travis O, and he said it was fixed in the
SVN.
thanks for the suggestions, I'll try them out now.
best
Sonja
Filip Wasilewski wrote:
> sonjaa wrote:
> > Hi
> >
> > last week I posted a problem with running out of memory when changing
&g