(forgot reply-to-all)
--- Begin Message ---
Yoav Avitzour wrote:
OK, thanks for the info. Is imshow currently the only array imaging
routine that supports this functionality?
You can also do it with pcolor, provided you flatten the array. This
was probably true with 0.87.7; I have verified
OK, thanks for the
info. Is imshow currently the only array imaging routine that supports
this functionality?
Thanks again,
Yoav
Eric Firing wrote:
The
contour routine does not have update functionality similar to that of
an image; you have no choice but to generate a new ContourSet obj
The contour routine does not have update functionality similar to that
of an image; you have no choice but to generate a new ContourSet object
each time.
Eric
Yoav Avitzour wrote:
> Hi,
>
>
> I'm trying to create 2D animations using contours. Is there a
> recommended way to do this? I was ho
Hi,
I'm trying to create 2D
animations using contours. Is there a recommended way to do this? I was
hoping to follow the same route as in the dynamic_image_gtkagg.py
example, but for some reason set_array doesn't work for me with
contour. It doesn't produce any error, but the figure just does
Gary Ruben wrote:
> Hi Mark,
> this thread may help:
> http://thread.gmane.org/gmane.comp.python.numeric.general/13399/focus=13421
>
> Essentially, pylab uses a compatibility layer to ease the task of
> supporting the three array packages - currently this uses the Numeric
> version of the ones a
On 4/24/07, Tommy Grav <[EMAIL PROTECTED]> wrote:
> I have a plot where the x axis ticks are given as
>
> 0.1 0.15 0.20 0.025 0.30 0.35
>
> with +3.732e2 given in the lower right of the axis.
> How can I force the ticks to have
> 373.3 373.35
>
It always helps if you give us complete ex
On 4/23/07, [EMAIL PROTECTED]
<[EMAIL PROTECTED]> wrote:
>
> I'm producing series of plots (spectograms) in a program loop using imshow
> and saving each plot to .png. Even though I close() each plot after each
> savefig(...), the memory does not appear to be freed up, and the memory
> useage goes
[EMAIL PROTECTED] wrote:
>
> I'm producing series of plots (spectograms) in a program loop using
> imshow and saving each plot to .png. Even though I close() each plot
> after each savefig(...), the memory does not appear to be freed up, and
> the memory useage goes up and up as the program ru
I have a plot where the x axis ticks are given as
0.1 0.15 0.20 0.025 0.30 0.35
with +3.732e2 given in the lower right of the axis.
How can I force the ticks to have
373.3 373.35
and so on?
Cheers
Tommy
-
Th
I recently attended a fantastic workshop by John Hunter and Fernando
Perez, and John pointed out that I really do want to play with the
axis objects directly. In case someone googles for this later on,
here's how to do it for two boxes:
ax = axes([0.1, 0.3, 0.8, 0.6])
plot(rand(12))
a2 = axes([0
Hi Mark,
this thread may help:
http://thread.gmane.org/gmane.comp.python.numeric.general/13399/focus=13421
Essentially, pylab uses a compatibility layer to ease the task of
supporting the three array packages - currently this uses the Numeric
version of the ones and zeros functions giving the be
Matthias Michler <[EMAIL PROTECTED]> writes:
> The result really surprises me (using module time):
> time >plot< 9.7 sec
> time >setp< 9.9 sec<- slower than plot!
> time >.set< 5.0 sec
>
> So my question is: Is this the expected / desired behaviour?
I think it is not surprising. The setp
Hello everybody,
to reset data I'm using pylab.setp instead of the methods line.set_xdata,
line.set_ydata believing there would be no obvious difference in behaviour.
(Maybe I not really get what is going on in matplotlib.artist.py.)
The taken time is of quite big importance to me because I reall
Hi,
a friend gave me the little example I attached.
He uses 'gca().images = []' to delete the images. I'm not sure about memory
usage of that method, but I think deleting images (using clf() or the above
way) is quite important, because otherwise one more image is drawn above the
existing ones
"Mark Bakker" <[EMAIL PROTECTED]> writes:
> Can this be fixed? Any explanation how this happens? Pylab just
> imports part of numpy, doesn't it?
It imports numerix, a compatibility layer for numeric, numarray and
numpy. I think the plan is to remove numerix soon and just use numpy,
but in the mea
Hello list -
I am confused about the part of numpy that pylab imports.
Apparently, pylab imports 'zeros', but not the 'zeros' from numpy, as it
returns integers by default, rather than floats.
The same holds for 'ones' and 'empty'.
Example:
from pylab import *
zeros(3)
array([0, 0, 0])
from nu
Mhm,
thank you for testing - it doesn't work here unless I scale everthing. Bug?
Linux,
numpy.__version__
'1.0.1'
matplotlib.__version__
'0.87.3'
-
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - t
17 matches
Mail list logo
