matplotlib-users Mailing List for matplotlib

John Hunter wrote:
>>>>>> "Christopher" == Christopher Barker <Chr...@no...> writes:
> Christopher> Just as a note, if you have Cairo, you have PS, PDF,
> Christopher> SVG, raster, and, indeed, native draw-to-the-screen
> Christopher> functionality.
> 
> Last I checked if I recall correctly, about a year ago, the PS backend
> merely dumped a raster image and didn't do real vector graphics. Has
> this changed?
There has been a LOT of work on Cairo in the last year, including the PS 
back-end. I'm just a lurker at this point, so I don't know how robust it 
is, but it supports vector operations for at least the common stuff. 
Here's part of a note posted in April to the mailing list:
"""
Is the output using image fallbacks in a case where you think it
shouldn't, (that is, your drawing doesn't have any fancy
translucence or something else that PostScript can't support
natively). In particular, I want to know if cairo is now using
fallbacks for something that was handled natively by the cairo 1.0
series.
"""
Which implies to me that it's working, and getting better.
My main thought about Cairo is that there is little point in duplicating 
the effort that the Cairo devs are doing, even if it doesn't support a 
feature or two that is needed. It's better to contribute to Cairo.
That is, unless, you are allergic to C (which I am mildly) or you have 
good reason to think that the whole framework of Cairo is inadequate.
-Chris
-- 
Christopher Barker, Ph.D.
Oceanographer
 		
NOAA/OR&R/HAZMAT (206) 526-6959 voice
7600 Sand Point Way NE (206) 526-6329 fax
Seattle, WA 98115 (206) 526-6317 main reception
Chr...@no...

Hello, I have a problem with the svn version of matplotlib. I don't know when 
this problem appeared but it was working before.
so the next script gave me an error message: 
import pylab
p = pylab.plot([1,2],[2,3],'o')
pylab.setp(p,markerfacecolor=(120,120,120),markersize=5,markeredgewidth=1.,zorder=50)
pylab.show()
the main error message is:
ValueError: to_rgb: Invalid rgb arg "(10.0, 10.0, 10.0)"
to_rgb: Invalid rgb arg "(10.0, 10.0, 10.0)"
but I don't understand why.
N.

On Monday 10 July 2006 14:08, Fernando Perez wrote:
> On 7/10/06, Darren Dale <dd...@co...> wrote:
> > Hi Fernando,
> >
> > I tried opening your example of a bad eps file produced with the xpdf
> > option, and it looks identical to the good example you sent. (I opened it
> > with both ggv, and gv.)
>
> My mistake, sorry: gv (on both my Fedora 3 and my ubuntu dapper
> machines) shows the xpdf one on a whole page, so that confused me.
> But you are right: they have the same bounding box, so once embedded
> in a latex document, they both show up just fine.
>
> There are some differences in the PS header for both, and that's
> probably what causes the difference in gv behavior which I mistook for
> a bbox error.
>
> Sorry for the noise: it looks like everything is in good shape now.
>
> Many thanks for all this work! I am just in the middle of finishing
> up a paper where I needed all of this, so your timing could not be
> better.
I'm glad we got it all straightened out. Thanks for finding that bug before 
version 0.88 was released.

On 7/10/06, Darren Dale <dd...@co...> wrote:
> Hi Fernando,
>
> I tried opening your example of a bad eps file produced with the xpdf option,
> and it looks identical to the good example you sent. (I opened it with both
> ggv, and gv.)
My mistake, sorry: gv (on both my Fedora 3 and my ubuntu dapper
machines) shows the xpdf one on a whole page, so that confused me.
But you are right: they have the same bounding box, so once embedded
in a latex document, they both show up just fine.
There are some differences in the PS header for both, and that's
probably what causes the difference in gv behavior which I mistook for
a bbox error.
Sorry for the noise: it looks like everything is in good shape now.
Many thanks for all this work! I am just in the middle of finishing
up a paper where I needed all of this, so your timing could not be
better.
Cheers,
f

I'm trying to draw a contour plot in a Tk gui with an accompanying colorbar.
The gui allows changing which contour is drawn. Some of the contours use a
different set of levels, so I'd like to update the colorbar whenever the
levels change. I don't need an automatic update -- what I'd like is to
manually specify a new set of tick locations. What is the best way to do
that? Thanks much,
Mark Johnson
Central College
Pella, IA

This is a known bug in ESP Ghostscript, not matplotlib. ESP version 8.15.02 
broke xpdf's pdftops program. I posted a bug report to the ESP website, and 
it has been fixed in their sources, but they havent made a new release since 
that time. Your options are either to drop back to ESP version 7.07 or use 
gpl or afpl ghostscript.
Darren
On Monday 10 July 2006 08:58, Pieter Dumon wrote:
> Sorry, forgot the actual PS file, which contains the actual error. Here it
> is
>
> On 7/10/06, Pieter Dumon <pie...@gm...> wrote:
> > On 7/10/06, Darren Dale <dd...@co...> wrote:
> > > Pieter Dumon wrote:
> > > > For example, this fails for me (it does work without xpdf and doing
> > > > ps2pdf afterwards):
> > > >
> > > > import matplotlib
> > > > matplotlib.use('PS')
> > > > import pylab
> > > >
> > > > pylab.rc('text',usetex=True)
> > > > pylab.rc('ps',usedistiller='xpdf')
> > > > pylab.figure()
> > > > pylab.plot((1,2,3),(4,5,6))
> > > > pylab.savefig("test")
> > > > pylab.show()
> > > >
> > > > When setting ps.usedistiller to xpdf, I get an empty (blank) ps
> > > > image. Without xpdf, I get a proper ps. This did work with
> > > > 0.87-2/numpy-0.9.6 (The Pdf backend works, but not with mathttext.)
> > >
> > > Please set your verbose level to debug-annoying in your rc settings and
> > > post the output. Also post your platform info, along with version info
> > > for xpdf, and ghostscript. I havent had any problems with xpdf.
> >
> > The debug output is in attachment. I don't see any errors, except for
> > the latex warning (but the problem is the same without usetex=True,
> > apparently)
> >
> > ESP Ghostscript 815.02 (2006年04月19日)
> > xpdf version 3.01
> > poppler-0.5.3
> >
> > System is a quite standard Gentoo Linux (x86), but with gcc-4.1.1
> > 2.6.16-gentoo-r9 #1 PREEMPT Tue Jun 6 10:38:13 CEST 2006 i686 Mobile
> > Intel(R) Pentium(R) 4 - M CPU 2.00GHz GNU/Linux
> >
> > Pieter
-- 
Darren S. Dale, Ph.D.
Cornell High Energy Synchrotron Source
Cornell University
200L Wilson Lab
Rt. 366 & Pine Tree Road
Ithaca, NY 14853
dd...@co...
office: (607) 255-9894
fax: (607) 255-9001

Sorry, forgot the actual PS file, which contains the actual error. Here it is
On 7/10/06, Pieter Dumon <pie...@gm...> wrote:
> On 7/10/06, Darren Dale <dd...@co...> wrote:
> > Pieter Dumon wrote:
> > > For example, this fails for me (it does work without xpdf and doing
> > > ps2pdf afterwards):
>
> > > import matplotlib
> > > matplotlib.use('PS')
> > > import pylab
> > >
> > > pylab.rc('text',usetex=True)
> > > pylab.rc('ps',usedistiller='xpdf')
> > > pylab.figure()
> > > pylab.plot((1,2,3),(4,5,6))
> > > pylab.savefig("test")
> > > pylab.show()
> > >
> > > When setting ps.usedistiller to xpdf, I get an empty (blank) ps image.
> > > Without xpdf, I get a proper ps. This did work with 0.87-2/numpy-0.9.6
> > > (The Pdf backend works, but not with mathttext.)
> > >
> > Please set your verbose level to debug-annoying in your rc settings and
> > post the output. Also post your platform info, along with version info
> > for xpdf, and ghostscript. I havent had any problems with xpdf.
>
> The debug output is in attachment. I don't see any errors, except for
> the latex warning (but the problem is the same without usetex=True,
> apparently)
>
> ESP Ghostscript 815.02 (2006年04月19日)
> xpdf version 3.01
> poppler-0.5.3
>
> System is a quite standard Gentoo Linux (x86), but with gcc-4.1.1
> 2.6.16-gentoo-r9 #1 PREEMPT Tue Jun 6 10:38:13 CEST 2006 i686 Mobile
> Intel(R) Pentium(R) 4 - M CPU 2.00GHz GNU/Linux
>
> Pieter
>
>
>

On 7/10/06, Darren Dale <dd...@co...> wrote:
> Pieter Dumon wrote:
> > For example, this fails for me (it does work without xpdf and doing
> > ps2pdf afterwards):
> > import matplotlib
> > matplotlib.use('PS')
> > import pylab
> >
> > pylab.rc('text',usetex=True)
> > pylab.rc('ps',usedistiller='xpdf')
> > pylab.figure()
> > pylab.plot((1,2,3),(4,5,6))
> > pylab.savefig("test")
> > pylab.show()
> >
> > When setting ps.usedistiller to xpdf, I get an empty (blank) ps image.
> > Without xpdf, I get a proper ps. This did work with 0.87-2/numpy-0.9.6
> > (The Pdf backend works, but not with mathttext.)
> >
> Please set your verbose level to debug-annoying in your rc settings and
> post the output. Also post your platform info, along with version info
> for xpdf, and ghostscript. I havent had any problems with xpdf.
The debug output is in attachment. I don't see any errors, except for
the latex warning (but the problem is the same without usetex=True,
apparently)
ESP Ghostscript 815.02 (2006年04月19日)
xpdf version 3.01
poppler-0.5.3
System is a quite standard Gentoo Linux (x86), but with gcc-4.1.1
2.6.16-gentoo-r9 #1 PREEMPT Tue Jun 6 10:38:13 CEST 2006 i686 Mobile
Intel(R) Pentium(R) 4 - M CPU 2.00GHz GNU/Linux
Pieter

Hi Fernando,
I tried opening your example of a bad eps file produced with the xpdf option, 
and it looks identical to the good example you sent. (I opened it with both 
ggv, and gv.)
Darren
On Sunday 09 July 2006 23:33, Fernando Perez wrote:
> On 7/9/06, Darren Dale <dd...@co...> wrote:
> > Would you send me an example of a file with a bad bbox and one that is
> > correct?
>
> Thanks for looking into this!
>
> f
-- 
Darren S. Dale, Ph.D.
Cornell High Energy Synchrotron Source
Cornell University
200L Wilson Lab
Rt. 366 & Pine Tree Road
Ithaca, NY 14853
dd...@co...
office: (607) 255-9894
fax: (607) 255-9001

Pieter Dumon wrote:
> Could the bug I submitted some time ago be related to this ? (1502970
> at http://sourceforge.net/tracker/?group_id=80706&atid=560720)
>
> For example, this fails for me (it does work without xpdf and doing
> ps2pdf afterwards):
> My poppler/xpdf installation should be allright
>
> import matplotlib
> matplotlib.use('PS')
> import pylab
>
> pylab.rc('text',usetex=True)
> pylab.rc('ps',usedistiller='xpdf')
> pylab.figure()
> pylab.plot((1,2,3),(4,5,6))
> pylab.savefig("test")
> pylab.show()
>
> ---
> Summary:
> matplotlib-0.87.3 with xpdf renders empty PS
> upraded to matplotlib-0.87-3/numpy-0.9.8.
>
> When setting ps.usedistiller to xpdf, I get an empty (blank) ps image.
> Without xpdf, I get a proper ps. This did work with 0.87-2/numpy-0.9.6
> (The Pdf backend works, but not with mathttext.)
> 
Please set your verbose level to debug-annoying in your rc settings and 
post the output. Also post your platform info, along with version info 
for xpdf, and ghostscript. I havent had any problems with xpdf.

Could the bug I submitted some time ago be related to this ? (1502970
at http://sourceforge.net/tracker/?group_id=80706&atid=560720)
For example, this fails for me (it does work without xpdf and doing
ps2pdf afterwards):
My poppler/xpdf installation should be allright
import matplotlib
matplotlib.use('PS')
import pylab
pylab.rc('text',usetex=True)
pylab.rc('ps',usedistiller='xpdf')
pylab.figure()
pylab.plot((1,2,3),(4,5,6))
pylab.savefig("test")
pylab.show()
---
Summary:
matplotlib-0.87.3 with xpdf renders empty PS
upraded to matplotlib-0.87-3/numpy-0.9.8.
When setting ps.usedistiller to xpdf, I get an empty (blank) ps image.
Without xpdf, I get a proper ps. This did work with 0.87-2/numpy-0.9.6
(The Pdf backend works, but not with mathttext.)
---
Bye,
Pieter
On 7/10/06, Fernando Perez <fpe...@gm...> wrote:
> On 7/9/06, Darren Dale <dd...@co...> wrote:
> > Would you send me an example of a file with a bad bbox and one that is
> > correct?
>
> Thanks for looking into this!
>
> f
>
>
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job easier
> Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
>
>
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>
>
>
>

On 7/9/06, Darren Dale <dd...@co...> wrote:
> Would you send me an example of a file with a bad bbox and one that is
> correct?
Thanks for looking into this!
f

Would you send me an example of a file with a bad bbox and one that is 
correct?
On Sunday 09 July 2006 10:28 pm, Fernando Perez wrote:
> On 7/9/06, Darren Dale <dd...@co...> wrote:
> > I think this is artifact results from a combination of the ghostscript
> > distiller and the postscript renderer. If you have xpdf on your system,
> > you can set ps.usedistiller : xpdf in rc. That will give you embeddable
> > eps files without converting the fonts to outlines (or whatever
> > ghostscript does), so they scale nicely. As a bonus, if you put the
> > figure in a pdf, the figure text will be searchable.
>
> Thanks for the tip! The result looks indeed very nice, but
> unfortunately the bounding box is all wrong (using ps.distiller=False
> gives eps files with the proper bounding box). With an incorrect
> bounding box, these eps files are kind of useless (not completely,
> since ps2eps can correct this, but it's annoying to have to fix every
> plot you make manually...)
>
>
> Any ideas?
>
> Cheers,
>
> f
>
>
> -------------------------------------------------------------------------
> Using Tomcat but need to do more? Need to support web services, security?
> Get stuff done quickly with pre-integrated technology to make your job
> easier Download IBM WebSphere Application Server v.1.0.1 based on Apache
> Geronimo
> http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
-- 
Darren S. Dale, Ph.D.
dd...@co...

On 7/9/06, Darren Dale <dd...@co...> wrote:
> I think this is artifact results from a combination of the ghostscript
> distiller and the postscript renderer. If you have xpdf on your system, you
> can set ps.usedistiller : xpdf in rc. That will give you embeddable eps files
> without converting the fonts to outlines (or whatever ghostscript does), so
> they scale nicely. As a bonus, if you put the figure in a pdf, the figure
> text will be searchable.
Thanks for the tip! The result looks indeed very nice, but
unfortunately the bounding box is all wrong (using ps.distiller=False
gives eps files with the proper bounding box). With an incorrect
bounding box, these eps files are kind of useless (not completely,
since ps2eps can correct this, but it's annoying to have to fix every
plot you make manually...)
Any ideas?
Cheers,
f