matplotlib-users Mailing List for matplotlib

Hi,
I am using matplotlib within a wxPython app. I have a class called 
plotDialog that inherits from wx.Dialog and contains a matplotlib 
FigureCanvas. Several types of plot classes derive from plotDialog 
and bring up pretty windows displaying data of various sources.
What I want to do is write a routine which generates a "report" -- 
namely a combination of multiple plots and some text. The format could be:
1. One colossal plotDialog with tons of stuff in it in subplots 
(hopefully implemented some other way besides duplicating all of the 
individual plot routines within one dialog).
2. A word (or some other format) document with a bunch of jpegs 
pasted into it (best)
3. A dialog with a bunch of jpegs pasted in to it.
Can anyone suggest a way to do this? Can python output images to a 
document (multiply, not just saving one jpeg)? Can matplotplib or 
wxPython paste an image from the clipboard (I know I can copy to it)?
Thanks for any ideas,
-mike

My key question is this:
Can't Visio import ANY standard vector graphics format: SVG, EPS, PDF, 
something? Or, for that matter, some Visio specific format that is a 
file format, rather than using COM to drive Visio itself.
I'm sure you considered this, but I'd be interested to know what went 
into the decision to do it this way.
-Chris
-- 
Christopher Barker, Ph.D.
Oceanographer
Emergency Response Division
NOAA/NOS/OR&R (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chr...@no...

On 2006年12月20日, John Hunter apparently wrote: 
> I added this to svn.
Thanks!
> When I got into the code, I saw there is already a way to 
> do this: 
> line.set_dashes((None, None)) 
Yes, in 0.87.7, this works. Thanks!
(Note that it works only for a tuple,
not for a list.)
Cheers,
Alan
PS Why you might want to do this:
across figures I want to set a consistent
set of line styles, globally specifying a list of
dash styles, one for every line.

>>>>> "Alan" == Alan G Isaac <ai...@am...> writes:
 Alan> On 2006年12月20日, John Hunter apparently wrote:
 >> Is this expected? I wouldn't expect it.
 Alan> It is pretty standard. See e.g. the PostScript Language
 Alan> Reference Manual. And, how else to set a solid line with
 Alan> set_dashes?
I added this to svn. When I got into the code, I saw there is already
a way to do this:
 line.set_dashes((None, None))
JDH

>>>>> "Alan" == Alan G Isaac <ai...@am...> writes:
 Alan> It is pretty standard. See e.g. the PostScript Language
 Alan> Reference Manual. And, how else to set a solid line with
 Alan> set_dashes?
I didn't know that about postscript. I can easily implement it if it
is "the right thing to do (tm)". But it never occurred to me to
implement a solid line with set_dashes. I would tend to do
 line.set_linestyle('-')
Since it is part of postscript, I'll make it the default for mpl too.
JDH

On 2006年12月20日, John Hunter apparently wrote: 
> Is this expected? I wouldn't expect it. 
It is pretty standard.
See e.g. the PostScript Language Reference Manual.
And, how else to set a solid line with set_dashes?
Cheers,
Alan Isaac

>>>>> "Alan" == Alan G Isaac <ai...@am...> writes:
 Alan> If ln is a Line2D then ln.set_dashes([]) does not give the
 Alan> expected solid line. version: 0.87.7
Is this expected? I wouldn't expect it. set_dashes is supposed to
take an even length sequence of off-on ink. Perhaps it should raise
an exception for an empty list.
JDH

If ln is a Line2D then
ln.set_dashes([])
does not give the expected solid line.
version: 0.87.7
Cheers,
Alan Isaac

Hi David,
On Wednesday 20 December 2006 12:17, David Levitan wrote:
> I'm trying to use the qt4agg backend and running into performance issues
> (both using matplotlib interactively and in a program). The performance
> of qtagg and gtkagg backends are fine and drawing a zoom rectangle, for
> example, is smooth. With qt4, however, dragging and zooming are very
> choppy. Is this is known bug and is there any way to work around this?
It may be an issue with your installation of qt4/PyQt4. Panning and zooming 
are both quite fast for me. I'm using qt-4.2.2 and PyQt-4.1 on a 64bit gentoo 
linux machine.
Darren

Hi,
I'm trying to use the qt4agg backend and running into performance issues 
(both using matplotlib interactively and in a program). The performance 
of qtagg and gtkagg backends are fine and drawing a zoom rectangle, for 
example, is smooth. With qt4, however, dragging and zooming are very 
choppy. Is this is known bug and is there any way to work around this?
Thanks,
David

I've done some prograss about visualising my plots from a function, but 
after searching in the FAQ and also in the amiling list archive i dint' 
find any solution to this.
I have a function that computes some data for a plot. I call the 
function and then use show.
Everything work fine.
Then I close all the figure (closing manually windows) and also using 
close() in the console (using IDLE) then I rerun the function because I 
need to make some changes.
But when I restart the function the precedent show() seems still active 
and make me all plots freeze.
Is there a way to "clean" the memory of matplotlib without restarting 
the shell. Because if I restart shell obviously I loose all the data the 
I need for redoing the calculation.
Any help very appreciated.
Giorgio

Darren Dale wrote:
> On Wednesday 20 December 2006 6:38 am, Toon Verstraelen wrote:
>> Hi,
>>
>> Is it possible to make multiline labels with mathtext? When I try this:
>>
>> pylab.title(r"$(a+b)^2\\(a-b)^2$")
>>
>> only the first line is rendered. Is there a way to do this properly?
> 
> It looks like this isn't possible right now with regular mathtext. I suggest 
> filing a request on the matplotlib sourceforge site, or even better, 
> submitting a patch. In the meantime, your example works with usetex: True.
> 
> Darren
Ok, I will take a look at it. Is the suggested syntax with the double 
backslash satisfactory? Should the patch be written for mathtext or for 
mathtext2?
greetz,
Toon

On Wednesday 20 December 2006 4:34 am, Nils Wagner wrote:
> How can I use amsmath in matplotlibrc ?
amsmath is not currently supported.
Darren

On Wednesday 20 December 2006 6:38 am, Toon Verstraelen wrote:
> Hi,
>
> Is it possible to make multiline labels with mathtext? When I try this:
>
> pylab.title(r"$(a+b)^2\\(a-b)^2$")
>
> only the first line is rendered. Is there a way to do this properly?
It looks like this isn't possible right now with regular mathtext. I suggest 
filing a request on the matplotlib sourceforge site, or even better, 
submitting a patch. In the meantime, your example works with usetex: True.
Darren

Hi,
Is it possible to make multiline labels with mathtext? When I try this:
pylab.title(r"$(a+b)^2\\(a-b)^2$")
only the first line is rendered. Is there a way to do this properly?
thanks,
Toon

I've succeded in solving the problem that seems due to usage of show.
Both of the function i called had a show function enabled that seems to 
confuse a bit the behaviour of matplotlib.
so I commented in both function show and only put it in the module that 
called both function.
Not to comfortable if you have to call a lot of function that use show 
command but it worked :)
Giorgio

 Hi,
How can I use amsmath in matplotlibrc ?
I would like to add a legend((r'$\det{\boldsymbol P}$')).
Nils

Hi there!
I implemented a Print method with gtk-2.10 PrintOperations... It was not
easy, because of some transformations issues inside matplotlib...
My wish is: The plot window navigation bar should provide a print button
in future. I think many people are missing this button.
Here, I want to provide code for printing the screen, just like the save
button on the navigation bar.
It is the merge of the save button's code and the code in
pygtk-2.10.1/examples/pygtk-demo/demos/print_editor.py
Maybe, there is already a lot of print code available for other GUI
backends, if it will be shared, it could become part of matplotlib...
Yours, Achim
(Sorry, I could not provide a running program, because I am short in
time. The code is working in a bigger project
http://www.fkp.physik.tu-darmstadt.de/damaris/ )

John Hunter wrote:
>
>
> David> In make_image, most of the time is taken into to_rgba:
> David> almost half of it is taken in by the take call in the
> David> Colormap.__call__. Almost 200 ms to get colors from the
> David> indexes seems quite a lot (this means 280 cycles / pixel on
> David> average !). I can reproduce this number by using a small
> David> numpy test.
>
> David> On my laptop (pentium M, 1.2 Ghz), make_image takes almost
> David> 85 % of the time, which seems to imply that this is where
> David> one should focus if one wants to improve the speed,
>
> This may have been lost in the longer thread above,
I am a bit lost myself between numpy and mpl ML, sorry for the 
inconvenience.
> but what
> interpolation are you using? You may see a good performance boost by
> using interpolation='nearest'. 
At what point is interpolation used ?
> Also, with your clip changes and with
> Eric's changes is it still painfully slow for you
Painfully is a strong word :) It is still 10 to 15 times slower than 
matlab on the same computer: the show call is around 800 ms instead of 
70 ms with matlab, and matlab image is equivalent to imshow + show calls 
actually. Matlab having only one toolkit, it obviously has an advantage, 
but I don't think the problem is on the GUI side anyway.
> -- how much have
> these changes helped? 
With the original profiling, it took a bit more than 2100 ms for a show 
call after a imshow call for a 8000x256 array according to a saved 
kcachegrind profile. Now, it is around 800 ms, which is already much 
better, and with minimal changes (eg without using a special fast path 
more prone to bugs). I estimate that squeezing to a bit less than 500 ms 
should be easily possible by improving on numpy side (clip, float to int 
convertion and take function), which has the nice effect of improving 
mpl without touching one line of it, and improving numpy as the same time :)
The last 500 ms would be much more difficult to squeeze: half of it is 
used to 'launch' the figure anyway. And below a few hundred ms, it is 
becoming unnoticeable in interactive use (whereas the change from 2.1 s 
to 0.8 is; on my laptop, it is even more noticeable, because its CPU is 
kind of slow).
David