matplotlib-devel Mailing List for matplotlib

"Jae-Joon Lee" <lee...@gm...> writes:
> Here is a patch which uses a preview package. It uses a "showbox"
> option in the preview package, with a slight tweak (this only patches
> the texmanager.py. You still need to apply the agg backend patch in my
> previous post). It would be good if this patch will be accepted, but
> the extra requirement of the preview package may need some dicussion.
> Although it seems that the preview package is commonly found with a
> TeX installation, I guess it is not part of the major TeX distribution
> (e.g. tetex, tex-live) yet. One way would be to make it as an optional
> feature.
FWIW, Debian provides preview.sty in the binary package
preview-latex-style (generated from the source package auctex).
Chris
> 
> 
> 
> On Fri, Aug 29, 2008 at 12:04 PM, Jae-Joon Lee <lee...@gm...> wrote:
> > Thanks,
> >
> > I quickly went through the code of the pngmath.py, and it seems that
> > the depth(descent) of the dvi file is reported by "dvipng" (but the
> > preview package must be used in the tex file for this to work
> > correctly). Therefore, with this method, we need to run dvipng even if
> > we use ps of pdf backend. Although this seems fine to me, I'll see if
> > I can extract the depth of the text without running the dvipng.
> >
> > Regards,
> >
> > -JJ
> >
> >
> >
> >
> > On Fri, Aug 29, 2008 at 7:59 AM, Michael Droettboom <md...@st...> wrote:
> >> Sphinx contains one way to do this in its new "pngmath" extension. It uses
> >> the LaTeX package "preview" which does all of this magic internally. And I
> >> believe it's a little more general. If I recall, the approach you're taking
> >> won't work with some LaTeX constructs such as:
> >>
> >> \begin{align}
> >> x & = 2
> >> y & = 2
> >> \end{align}
> >>
> >> Plus, Sphinx is BSD-licensed, so it should be fine to copy-and-paste
> >> whatever code is necessary.
> >>
> >> Of course, latex-preview is required to be installed, but I think it's a
> >> pretty common package.
> >>
> >> See here:
> >>
> >> http://svn.python.org/projects/doctools/trunk/sphinx/ext/pngmath.py
> >>
> >> Cheers,
> >> Mike
> >>
> >> Jae-Joon Lee wrote:
> >>>
> >>> On Thu, Aug 28, 2008 at 4:18 PM, John Hunter <jd...@gm...> wrote:
> >>>
> >>>>
> >>>> On Thu, Aug 28, 2008 at 2:57 PM, Jae-Joon Lee <lee...@gm...>
> >>>> wrote:
> >>>>
> >>>>
> >>>>>
> >>>>> First of all, I borrowed this idea from the PyX which is in GPL.
> >>>>> Although there is little of copying, other than the basic idea, I'm
> >>>>> not 100% sure if this could be BSD-compatible.
> >>>>>
> >>>>
> >>>> I think it is fine to borrow the idea; what we need to do is a clean
> >>>> room implementation with no copying. You can best answer that, so if
> >>>> you tell us your patch is cleanly implemented, we can accept it.
> >>>>
> >>>> JDH
> >>>>
> >>>>
> >>>
> >>> Thanks for the response.
> >>>
> >>> Well, the only part I borrowed from PyX is TeX related commands they
> >>> use (there is not much of implementation as far as TeX-related code is
> >>> concerned). From their code, I learned the meaning and usage of the
> >>> following TeX commands
> >>>
> >>> \newbox
> >>> \setbox
> >>> \immediate\write16
> >>>
> >>> And I used the same TeX commands in my code.
> >>> But I personally think this is not a (code) copy.
> >>>
> >>> Other than this, the code is clean.
> >>> Regards,
> >>>
> >>> -JJ
> >>>
> >>> -------------------------------------------------------------------------
> >>> This SF.Net email is sponsored by the Moblin Your Move Developer's
> >>> challenge
> >>> Build the coolest Linux based applications with Moblin SDK & win great
> >>> prizes
> >>> Grand prize is a trip for two to an Open Source event anywhere in the
> >>> world
> >>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
> >>> _______________________________________________
> >>> Matplotlib-devel mailing list
> >>> Mat...@li...
> >>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
> >>>
> >>
> >>
> >
> 
> -------------------------------------------------------------------------
> This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
> Build the coolest Linux based applications with Moblin SDK & win great prizes
> Grand prize is a trip for two to an Open Source event anywhere in the world
> http://moblin-contest.org/redirect.php?banner_id=100&url=/_______________________________________________
> Matplotlib-devel mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Here is a patch which uses a preview package. It uses a "showbox"
option in the preview package, with a slight tweak (this only patches
the texmanager.py. You still need to apply the agg backend patch in my
previous post). It would be good if this patch will be accepted, but
the extra requirement of the preview package may need some dicussion.
Although it seems that the preview package is commonly found with a
TeX installation, I guess it is not part of the major TeX distribution
(e.g. tetex, tex-live) yet. One way would be to make it as an optional
feature.
Regards,
-JJ
On Fri, Aug 29, 2008 at 12:04 PM, Jae-Joon Lee <lee...@gm...> wrote:
> Thanks,
>
> I quickly went through the code of the pngmath.py, and it seems that
> the depth(descent) of the dvi file is reported by "dvipng" (but the
> preview package must be used in the tex file for this to work
> correctly). Therefore, with this method, we need to run dvipng even if
> we use ps of pdf backend. Although this seems fine to me, I'll see if
> I can extract the depth of the text without running the dvipng.
>
> Regards,
>
> -JJ
>
>
>
>
> On Fri, Aug 29, 2008 at 7:59 AM, Michael Droettboom <md...@st...> wrote:
>> Sphinx contains one way to do this in its new "pngmath" extension. It uses
>> the LaTeX package "preview" which does all of this magic internally. And I
>> believe it's a little more general. If I recall, the approach you're taking
>> won't work with some LaTeX constructs such as:
>>
>> \begin{align}
>> x & = 2
>> y & = 2
>> \end{align}
>>
>> Plus, Sphinx is BSD-licensed, so it should be fine to copy-and-paste
>> whatever code is necessary.
>>
>> Of course, latex-preview is required to be installed, but I think it's a
>> pretty common package.
>>
>> See here:
>>
>> http://svn.python.org/projects/doctools/trunk/sphinx/ext/pngmath.py
>>
>> Cheers,
>> Mike
>>
>> Jae-Joon Lee wrote:
>>>
>>> On Thu, Aug 28, 2008 at 4:18 PM, John Hunter <jd...@gm...> wrote:
>>>
>>>>
>>>> On Thu, Aug 28, 2008 at 2:57 PM, Jae-Joon Lee <lee...@gm...>
>>>> wrote:
>>>>
>>>>
>>>>>
>>>>> First of all, I borrowed this idea from the PyX which is in GPL.
>>>>> Although there is little of copying, other than the basic idea, I'm
>>>>> not 100% sure if this could be BSD-compatible.
>>>>>
>>>>
>>>> I think it is fine to borrow the idea; what we need to do is a clean
>>>> room implementation with no copying. You can best answer that, so if
>>>> you tell us your patch is cleanly implemented, we can accept it.
>>>>
>>>> JDH
>>>>
>>>>
>>>
>>> Thanks for the response.
>>>
>>> Well, the only part I borrowed from PyX is TeX related commands they
>>> use (there is not much of implementation as far as TeX-related code is
>>> concerned). From their code, I learned the meaning and usage of the
>>> following TeX commands
>>>
>>> \newbox
>>> \setbox
>>> \immediate\write16
>>>
>>> And I used the same TeX commands in my code.
>>> But I personally think this is not a (code) copy.
>>>
>>> Other than this, the code is clean.
>>> Regards,
>>>
>>> -JJ
>>>
>>> -------------------------------------------------------------------------
>>> This SF.Net email is sponsored by the Moblin Your Move Developer's
>>> challenge
>>> Build the coolest Linux based applications with Moblin SDK & win great
>>> prizes
>>> Grand prize is a trip for two to an Open Source event anywhere in the
>>> world
>>> http://moblin-contest.org/redirect.php?banner_id=100&url=/
>>> _______________________________________________
>>> Matplotlib-devel mailing list
>>> Mat...@li...
>>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>>>
>>
>>
>

On Tue, Sep 2, 2008 at 10:40 AM, Paul Kienzle <pki...@ni...> wrote:
> Speed improvements in the matplotlib front end may be possible, for
> example by representing tics and grids as line collections rather than
> rendering each one with a separate path command.
I think the big win here would be for us to write a light-weight axis
support which doesn't have all the features of the default axis but is
fast. Eg, it would not support all the various alignment and
rotations for ticklabels (eg, all xtick labels would be horizontally
aligned center and top aligned vertical) and would have homogeneous
font properties (don't create a bunch of Text instances, just call
draw_text repeatedly with the labels. We could drop the locators and
formatters and mathtext and all that, and make the user responsible
for setting the locations and label strings. We would not have
separate objects for each tick, but just draw all the markers in the
right places using a single plot command with linestyle TICK_LEFT,
etc.). This would probably be fast enough for most quasi-realtime
plots.
I think one could use Michael's projection registry to support this
kind of thing, even though it is not a projection the infrastructure
could be used to support pluggable axis support. This is on my TODO
list, but I probably cannot get to it right away.
JDH

On Mon, Sep 01, 2008 at 12:06:45AM -0700, Kevinsysu wrote:
> 
> Hi all:
> 
> I'm using matplotlib for plotting in recent days. I love it especially the
> usability and the plot quality.
> 
> My current work is to display a real time data set update into several 2D
> graphs (5 or more, 400x400 graphs).
> The environment I'm using is:
> wxpython 2.8.8.1
> matplotlib 0.98.3
> python 2.5.1.1
> Intel P IV 2.4G
> Using the wxagg backend.
> 
> The issue I encoutered was that the graphs refresh took too much CPU time,
> or in other word, the graph is not draw fast enough.
> Sorry to raise this performance topic again, as I knew you've discussed a
> lot on this topic, there're also some posts related to this, but I just
> can't find a solution suite to me.
> 
> For single graph sized 400x400, my target is to reach 50 fps. Actually, it
> can be easily achieved using the animation method: copy_from_bbox/
> restore_region in the following link.
> http://www.scipy.org/Cookbook/Matplotlib/Animations. (I reach 90+ fps with
> this) The difficulty I got is that the above method is only updating the
> bbox area, but I have to update the x/y axis as well. As John indicated in
> another post, updating the x/y axis is the bottleneck of the draw process.
> When I update the x/y axis at the same time, the performance drops to 20+
> fps, which is lower than my requirement.
> 
> Below are my questions, any kind of answer or hints would be appreciated:
> 1.	Can I reach the performance requirement by using the wxagg? If yes, how
> can I get there?
> 2.	Is there any existing backend can reach the performance requirement? Can
> it be embedded with wxpython?
> 3.	What differences (especially performance aspect) between the wxagg and
> agg backend? 
> 4.	As I know, in the recent post, Paul Kienzle is planning to develop the
> opengl backend. Could the opengl backend have a great improvement on
> performance compare with the wxagg?
You can figure out how much time is involved on the front side matplotlib
by using the null backend Template:
 import matplotlib
 matplotlib.use('Template')
This will give you an upper limit on your performance since none of the
rendering costs are shown. If that is already down to e.g., 30 fps then
you will not see anything better from an opengl backend.
Speed improvements in the matplotlib front end may be possible, for
example by representing tics and grids as line collections rather than
rendering each one with a separate path command.
	- Paul