matplotlib-users Mailing List for matplotlib

Jeff, 
I agree with John -- matplotlib and the wxAgg backend 
don't seem slow to me. For simple line drawings in 
'stripchart mode', where a line is being updated as 
fast as possible, I regularly get ~12 plots per second
with wxAgg and mpl 0.81+ on Windows. It's hard for me 
to consider that slow, but you weren't specific about 
what you were expecting.
Do the examples at 
 http://cars.uchicago.edu/~newville/Python/MPlot 
help? MPlot gives a wxPanel and wxFrame for simple line 
drawings that gives GUI-controlled customization of line 
color and style, etc and provides simple ways for end 
users to zoom in/out, print, and saving of images. The 
examples/test.py includes a stripchart-like plot.
--Matt

When I create a plot that is smaller than the figure window, the tickmark=
=20
locator seems to locate the ticks based on the figure size, not the subplot=
=20
size. I tried this several ways.
figure(figsize=3D(3,3))
plot([1000,2000,3000],[1,2,3])
subplots_adjust(right=3D0.5)
This messes up the ticklabels, especially on the x-axis. It should resample=
=20
and only plot a couple of ticks, but I don't know the command to update the=
=20
ticks. The same happens when I resize with the tool on the toolbar. Almost=
=20
the same happens when I use the axes command from the get go:
figure(figsize=3D(3,3))
axes( [.1,.1,.4,.8] )
plot([1000,2000,3000],[1,2,3])
This give fine looking y labels, but the x-axis is still messed up. Does it=
=20
maybe always plot 4 ticks on each axis by default? Should it maybe check if=
=20
there is space for that?
Any suggestions are appreciated,
Thanks,
Mark

>>>>> "Darren" =3D=3D Darren Dale <dd...@co...> writes:
 Darren> Also, if you provide a brief example script, along with
 Darren> any relevant changes you have made to matplotlibrc, and
 Darren> some detail about how long it takes to plot (maybe some
 Darren> profiling?), we might be able to provide some more useful
 Darren> suggestions.
A script is by far the most useful thing you can provide. =20
Note that there was an optimization for line marker drawing on win32
introduced in matplotlib-0.81 From the release notes:
 Fast markers on win32 The marker cache optimization is finally
 available for win32, after an agg bug was found and fixed (thanks
 Maxim!). Line marker plots should be considerably faster now on
 win32. The original optimization announcement is ay
 http://matplotlib.sourceforge.net/whats_new.html#0.72-line_marker_opti=
mizations_in_agg
See also http://matplotlib.sourceforge.net/faq.html#SLOW
JDH
=00

On Thursday 30 June 2005 11:15 am, Jeff Peery wrote:
> Hello,
>
> I wrote a small WXAgg program with wxpython. I'm plotting simple
> datasets, right now I'm plotting an array of approx. 450 points. The
> graphing is very slow. What can I do to speed this up? I have python
> 2.4, wxpython 2.4, and this is what I'm using for matplotlib
> 'matplotlib-0.80.win32-py2.4.exe'.
Have you checked the list archives? There has been some discussion about speed 
traps that you can take steps to avoid. For example, are you running a script 
with interactive mode on? That can cause a big performance hit. 
Also, if you provide a brief example script, along with any relevant changes 
you have made to matplotlibrc, and some detail about how long it takes to 
plot (maybe some profiling?), we might be able to provide some more useful 
suggestions.
-- 
Darren

Hello, 
I wrote a small WXAgg program with wxpython. I'm plotting simple
datasets, right now I'm plotting an array of approx. 450 points. The
graphing is very slow. What can I do to speed this up? I have python
2.4, wxpython 2.4, and this is what I'm using for matplotlib
'matplotlib-0.80.win32-py2.4.exe'.
Thanks.
Jeff

James Boyle writes:
[snip]
 > For values outside the range of the max and min of the normalization, I 
 > have added filled triangles above and below the color bar.
 > This type of display is found in other visualization software. It 
 > allows the scale to just consider values of interest, while providing 
 > information as to the location and relative values of outliers.
I'd also find this very useful. For comparison, there is something
similar (colorscale) on the matlab central file exchange:
http://tinyurl.com/8yzbe
but it looks like it was broken in the change from R13 to R14. Not
that I can be of any use adding this, but colorscale also has a nice
feature that:
"The colormap may contain special values for null data areas, and
these special values may be excluded from the scale bar. Or, the
colormap may be deliberately partitioned and shared with a different
image in the same figure, and that image may have its own, entirely
distinct, color scale."
There's a nice walkthrough here:
http://www.mathworks.com/company/newsletters/digest/nov02/earth.html
Regards, Phil