Perry Greenfield wrote:
> To give an idea, when you ask matplotlib to render an image, it
> processes it (resamples, rescales, maps to colors, etc) in order to
> actually display it. Since it may redo all that if you resize or
> otherwise re-render the figure, it needs to keep a reference to t
s around, then the original images are still there. But it's hard
> to know what's going on without the details. It sure sounds like the
> original arrays are still around somewhere.
>
> Thanks, Perry
>
> On Dec 15, 2009, at 11:54 AM, Wellenreuther, Gerd wrote:
>
Dear all,
I am trying to write a script to be used with our microscope, stitching
images of various magnifications together to yield a big picture of a
sample. The preprocessing involves operations like rotating the picture
etc., and finally those pictures are being plotted using imshow.
Unfor
only
using 100MB.
Cheers, Gerd
Wellenreuther, Gerd wrote:
> Dear all,
>
> I just again faced a problem appearing whenever I quickly generate
> multiple plots (using Windows XP, Python 2.5, matplotlib 0.98.1):
>
>> pylab.ion()
>> for n in range(n_elements):
&g
Dear all,
I just again faced a problem appearing whenever I quickly generate
multiple plots (using Windows XP, Python 2.5, matplotlib 0.98.1):
>
> pylab.ion()
> for n in range(n_elements):
> ##print
> ##print element_symbols[n]+'-'+element_linegroup[n]
> ##print normalized_mass_frac
