matplotlib-users Mailing List for matplotlib (Page 10)

what about the mplot3d. (http://www.scipy.org/Cookbook/Matplotlib/mplot3D)
it works nice under matplotlib0.86.2
but it can't work under matplotlib 0.87.3(with numpy or numeric).

On 7/12/06, Charlie Moad <cw...@gm...> wrote:
> On 7/7/06, John Hunter <jdh...@ac...> wrote:
> >
> > We'd like to do a bugfix release for the next release of enthought
> > python, which will include the latest mpl.  Apparently, there is a
> > problem with 0.87.3 and numpy which has been fixed in svn.
> >
> > If there is anything we should wait on, let us know, otherwise we'll
> > probably try to roll out 0.87.4 early next week.
> >
> > Thanks,
> > JDH
>
> http://cheeseshop.python.org/pypi/matplotlib/
> http://sourceforge.net/project/showfiles.php?group_id=80706
>
> ===============================================================
> 2006-07-11 Released 0.87.4 at revision 2558
>
> 2006-07-07 Fixed a usetex bug with older versions of latex - DSD
>
> 2006-07-07 Add compatibility for NumPy 1.0 - TEO
>
> 2006-06-29 Added a Qt4Agg backend. Thank you James Amundson - DSD
>
> 2006-06-26 Fixed a usetex bug. On windows, usetex will prcess
>           postscript output in the current directory rather than
>           in a temp directory. This is due to the use of spaces
>           and tildes in windows paths, which cause problems with
>           latex. The subprocess module is no longer used. - DSD
>
> 2006-06-22 Various changes to bar(), barh(), and hist().
>           Added 'edgecolor' keyword arg to bar() and barh().
>           The x and y args in barh() have been renamed to width
>           and bottom respectively, and their order has been swapped
>           to maintain a (position, value) order ala matlab. left,
>           height, width and bottom args can now all be scalars or
>           sequences. barh() now defaults to edge alignment instead
>           of center alignment. Added a keyword arg 'align' to bar(),
>           barh() and hist() that controls between edge or center bar
>           alignment. Fixed ignoring the rcParams['patch.facecolor']
>           for bar color in bar() and barh(). Fixed ignoring the
>           rcParams['lines.color'] for error bar color in bar()
>           and barh(). Fixed a bug where patches would be cleared
>           when error bars were plotted if rcParams['axes.hold']
>           was False. - MAS
>
> 2006-06-22 Added support for numerix 2-D arrays as alternatives to
>           a sequence of (x,y) tuples for specifying paths in
>           collections, quiver, contour, pcolor, transforms.
>           Fixed contour bug involving setting limits for
>           color mapping.  Added numpy-style all() to numerix. - EF
>
> 2006-06-20 Added custom FigureClass hook to pylab interface - see
>           examples/custom_figure_class.py
>
> 2006-06-16 Added colormaps from gist (gist_earth, gist_stern,
>           gist_rainbow, gist_gray, gist_yarg, gist_heat, gist_ncar) - JW
>
> 2006-06-16 Added a pointer to parent in figure canvas so you can
>           access the container with fig.canvas.manager.  Useful if
>           you want to set the window title, eg in gtk
>           fig.canvas.manager.window.set_title, though a GUI neutral
>           method would be preferable JDH
>
> 2006-06-16 Fixed colorbar.py to handle indexed colors (i.e.,
>           norm = no_norm()) by centering each colored region
>           on its index. - EF
>
> 2006-06-15 Added scalex and scaley to Axes.autoscale_view to support
>           selective autoscaling just the x or y axis, and supported
>           these command in plot so you can say plot(something,
>           scaley=False) and just the x axis will be autoscaled.
>           Modified axvline and axhline to support this, so for
>           example axvline will no longer autoscale the y axis. JDH
>
> 2006-06-13 Fix so numpy updates are backward compatible - TEO
>
> 2006-06-12 Updated numerix to handle numpy restructuring of
>           oldnumeric - TEO
>
> 2006-06-12 Updated numerix.fft to handle numpy restructuring
>           Added ImportError to numerix.linear_algebra for numpy -TEO
>
> 2006-06-11 Added quiverkey command to pylab and Axes, using
>           QuiverKey class in quiver.py.  Changed pylab and Axes
>           to use quiver2 if possible, but drop back to the
>           newly-renamed quiver_classic if necessary.  Modified
>           examples/quiver_demo.py to illustrate the new quiver
>           and quiverkey.  Changed LineCollection implementation
>           slightly to improve compatibility with PolyCollection. - EF
>
> 2006-06-11 Fixed a usetex bug for windows, running latex on files
>           with spaces in their names or paths was failing - DSD
>
> 2006-06-09 Made additions to numerix, changes to quiver to make it
>           work with all numeric flavors. - EF
>
> 2006-06-09 Added quiver2 function to pylab and method to axes,
>           with implementation via a Quiver class in quiver.py.
>           quiver2 will replace quiver before the next release;
>           it is placed alongside it initially to facilitate
>           testing and transition. See also
>           examples/quiver2_demo.py. - EF
>
> 2006-06-08 Minor bug fix to make ticker.py draw proper minus signs
>           with usetex - DSD
>
>
> -------------------------------------------------------------------------
> 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/7/06, John Hunter <jdh...@ac...> wrote:
>
> We'd like to do a bugfix release for the next release of enthought
> python, which will include the latest mpl.  Apparently, there is a
> problem with 0.87.3 and numpy which has been fixed in svn.
>
> If there is anything we should wait on, let us know, otherwise we'll
> probably try to roll out 0.87.4 early next week.
>
> Thanks,
> JDH

http://cheeseshop.python.org/pypi/matplotlib/
http://sourceforge.net/project/showfiles.php?group_id=80706

===============================================================
2006-07-11 Released 0.87.4 at revision 2558

2006-07-07 Fixed a usetex bug with older versions of latex - DSD

2006-07-07 Add compatibility for NumPy 1.0 - TEO

2006-06-29 Added a Qt4Agg backend. Thank you James Amundson - DSD

2006-06-26 Fixed a usetex bug. On windows, usetex will prcess
           postscript output in the current directory rather than
           in a temp directory. This is due to the use of spaces
           and tildes in windows paths, which cause problems with
           latex. The subprocess module is no longer used. - DSD

2006-06-22 Various changes to bar(), barh(), and hist().
           Added 'edgecolor' keyword arg to bar() and barh().
           The x and y args in barh() have been renamed to width
           and bottom respectively, and their order has been swapped
           to maintain a (position, value) order ala matlab. left,
           height, width and bottom args can now all be scalars or
           sequences. barh() now defaults to edge alignment instead
           of center alignment. Added a keyword arg 'align' to bar(),
           barh() and hist() that controls between edge or center bar
           alignment. Fixed ignoring the rcParams['patch.facecolor']
           for bar color in bar() and barh(). Fixed ignoring the
           rcParams['lines.color'] for error bar color in bar()
           and barh(). Fixed a bug where patches would be cleared
           when error bars were plotted if rcParams['axes.hold']
           was False. - MAS

2006-06-22 Added support for numerix 2-D arrays as alternatives to
           a sequence of (x,y) tuples for specifying paths in
           collections, quiver, contour, pcolor, transforms.
           Fixed contour bug involving setting limits for
           color mapping.  Added numpy-style all() to numerix. - EF

2006-06-20 Added custom FigureClass hook to pylab interface - see
           examples/custom_figure_class.py

2006-06-16 Added colormaps from gist (gist_earth, gist_stern,
           gist_rainbow, gist_gray, gist_yarg, gist_heat, gist_ncar) - JW

2006-06-16 Added a pointer to parent in figure canvas so you can
           access the container with fig.canvas.manager.  Useful if
           you want to set the window title, eg in gtk
           fig.canvas.manager.window.set_title, though a GUI neutral
           method would be preferable JDH

2006-06-16 Fixed colorbar.py to handle indexed colors (i.e.,
           norm = no_norm()) by centering each colored region
           on its index. - EF

2006-06-15 Added scalex and scaley to Axes.autoscale_view to support
           selective autoscaling just the x or y axis, and supported
           these command in plot so you can say plot(something,
           scaley=False) and just the x axis will be autoscaled.
           Modified axvline and axhline to support this, so for
           example axvline will no longer autoscale the y axis. JDH

2006-06-13 Fix so numpy updates are backward compatible - TEO

2006-06-12 Updated numerix to handle numpy restructuring of
           oldnumeric - TEO

2006-06-12 Updated numerix.fft to handle numpy restructuring
           Added ImportError to numerix.linear_algebra for numpy -TEO

2006-06-11 Added quiverkey command to pylab and Axes, using
           QuiverKey class in quiver.py.  Changed pylab and Axes
           to use quiver2 if possible, but drop back to the
           newly-renamed quiver_classic if necessary.  Modified
           examples/quiver_demo.py to illustrate the new quiver
           and quiverkey.  Changed LineCollection implementation
           slightly to improve compatibility with PolyCollection. - EF

2006-06-11 Fixed a usetex bug for windows, running latex on files
           with spaces in their names or paths was failing - DSD

2006-06-09 Made additions to numerix, changes to quiver to make it
           work with all numeric flavors. - EF

2006-06-09 Added quiver2 function to pylab and method to axes,
           with implementation via a Quiver class in quiver.py.
           quiver2 will replace quiver before the next release;
           it is placed alongside it initially to facilitate
           testing and transition. See also
           examples/quiver2_demo.py. - EF

2006-06-08 Minor bug fix to make ticker.py draw proper minus signs
           with usetex - DSD

>>>>> "Fernando" == Fernando Perez <fpe...@gm...> writes:

    Fernando> In my humble defense, the fact that this is barely
    Fernando> mentioned in the pylab tutorial, not at all in the plot
    Fernando> docstring, and also not in Perry's tutorial, may have
    Fernando> something to do with my not knowing about it ;)

You don't need any defense -- it's no secret that mpl is
under-documented.  If you know how to look, the information is usually
there, but the trick is knowing how to look

In [3]: l, = plot([1,2,3])

In [4]: setp(l)
    alpha: float
    animated: [True | False]
    antialiased or aa: [True | False]
    clip_box: a matplotlib.transform.Bbox instance
    clip_on: [True | False]
    color or c: any matplotlib color - see help(colors)
    dash_capstyle: ['butt' | 'round' | 'projecting']
    dash_joinstyle: ['miter' | 'round' | 'bevel']
    dashes: sequence of on/off ink in points
    data: (array xdata, array ydata)
    figure: a matplotlib.figure.Figure instance
    label: any string
    linestyle or ls: [ '-' | '--' | '-.' | ':' | 'steps' | 'None' ]
    linewidth or lw: float value in points
    lod: [True | False]
    marker: [ '+' | ',' | '.' | '1' | '2' | '3' | '4' | '<' | '>' |
    'D' | 'H' | '^' | '_' | 'd' | 'h' | 'o' | 'p' | 's' | 'v' | 'x' |
    '|' ]
    markeredgecolor or mec: any matplotlib color - see help(colors)
    markeredgewidth or mew: float value in points
    markerfacecolor or mfc: any matplotlib color - see help(colors)
    markersize or ms: float
    solid_capstyle: ['butt' | 'round' |  'projecting']
    solid_joinstyle: ['miter' | 'round' | 'bevel']
    transform: a matplotlib.transform transformation instance
    visible: [True | False]
    xdata: array
    ydata: array
    zorder: any number


This reminds me -- of late I've been wishing for a grep-like feature
in ipython

  In [2]: setp(l) | grep dash

to see just the output of setp that matches "dash".  In your case, you
would have seen

    dash_capstyle: ['butt' | 'round' | 'projecting']
    dash_joinstyle: ['miter' | 'round' | 'bevel']
    dashes: sequence of on/off ink in points

suggesting that you can not only configure the dash style, but the
dash cap and join style as well :-)

Of course, I could add this functionality to setp but it would be more
generally useful to have it in ipython.

The use case I had in mind today was in history, when I had a bunch of
commands I wanted to grep through

  In [1000]: history | grep xxx

JDH

On 7/10/06, John Hunter <jdh...@ac...> wrote:
> >>>>> "Fernando" == Fernando Perez <fpe...@gm...> writes:
>
>     Fernando> Hi all, this is somewhat of a half-feature request,
>     Fernando> half-question.  I just went through a rather unpleasant
>     Fernando> exercise in trying to get a line plot with about 8
>     Fernando> traces generated for black and white printing.  As it
>     Fernando> turns out, mpl seems to only have 4 line styles ('-',
>     Fernando> '--', '-.', ':'), which isn't really a whole lot
>     Fernando> (compare this to gnuplot's extensive dashing support).
>
> Are you aware of the "dashes" property, which allows you to set the
> exact dash pattern you want.  It's an arbitrary length sequence of
> alternating ink-on, ink-off, in points

In my humble defense, the fact that this is barely mentioned in the
pylab tutorial, not at all in the plot docstring, and also not in
Perry's tutorial, may have something to do with my not knowing about
it ;)

> # 5 points on, 2 off, 10 on, 5 off)
> plot(arange(20), '--', dashes=[5,2,10,5])
>
>     Fernando> Additionally, I'd like to suggest having a b/w mode,
>     Fernando> where mpl's auto-selection of different colors for
>     Fernando> successive line plots becomes a rotation of dashing
>     Fernando> modes.  Gnuplot's EPS backend has exactly this feature,
>
> This seems like a good idea -- if you define a nice sequence of dashes
> you want to cycle through, I'll build the rest of the infrastructure
> and make a figure property like iscolor.

Here's a specific, backwards-compatible proposal: why not add a new
format string type, '-N', with N running 0-9, and '-0' being identical
to a '-' (i.e., a continuous line).  I think that having easy access
to continuous plus 9 dashing patterns should be enough for most
purposes (a plot with more than 10 traces on it is just unreadable
anyway).  This mode also makes it code-friendly, so that one can
easily select any of the patterns with code of the type

  '-%s' % n

where n is being looped over, or a key from a dict, whatever.

I'm not quite sure what the best 9 patterns should be, so I'm
attaching a script to make it  easy to test a bunch of them in a
hurry.  This can help us find 9 distinctive ones (the gnuplot ones are
good, but I think we can do better), to put them into this basic list.
 The little script can also be added to the examples dir to showcase
the 9 basic patterns once selected (and you can make a figure for the
tutorial with it :)

Cheers,

f

On 7/11/06, Gary Ruben <gr...@bi...> wrote:
> On this topic, here is something I used the other day (just some
> different dash sequences):
>
> e, = plot(x, y, 'k', label=r'$\theta_3=%1.2f$'%(th3))
> setp(e, dashes={0:(1,0), 1:(2,2), 2:(10,4), 3:(10,4,4,4), 4:(10,2,2,2),
> 5:(15,2,6,2)}[i])

Thanks for these.  In playing with this, both for my needs and to try
and contribute something for a permanent solution, I found something
really strange.  Try running the following code in pylab:

"""Simple dashing test."""

import numpy as N
import pylab as P

dashes= { 0:(1,0),
          1:(2,2),
          2:(10,4),
          3:(10,4,4,4),
          4:(10,2,2,2),
          5:(15,2,6,2) }

y = N.ones(10)+N.rand(10)

P.figure()

dashnums = dashes.keys()
dashnums.sort()
for d in dashnums:
    P.plot(y,dashes=dashes[d])
    # Bug??? Using this, nothing gets displayed:
    y += 1
    # But with this, it works fine:
    #y = y+1

P.show()
# EOF


Uncomment the 'y=y+1' option, and all works fine.  Here's where the
problem may be coming from, just try this in a terminal:

y = 1.0*arange(10)
plot(y)
y += rand(10)
show()

There are actually two issues here, one is definitely a bug, the other
one could be construed as a feature (albeit a surprising one):

- bug: that the script above doesn't display anything with current
SVN.  I don't know why.

- feature?: that mpl holds on to the actual numpy memory buffer, so if
an array is modified in-place, any subsequent window update will
modify the plot.  I can actually see this being quite useful for
monitoring a region of memory, though it can cause surprising behavior
if you are just trying to get successive plots.  I guess I'm squarely
+1/-1 on how much I like it :)

I'll work a bit more on the dashing and send something later...

Cheers, and thanks for the hints!

f

Anyone know what happened to matplotlib.ticker.IndexFormatter? Is there are
replacement for it?

-- 
David Grant
Please Note my new email address: dav...@gm...

you can use the zorder option:

plot(x_line,y_line,zorder=3D10)
scatter(x_point,y_point,zorder=3D12)


N.

Le mardi 11 juillet 2006 14:48, aonghus a =E9crit=A0:
> Hi,
>
> I would like to draw a line, and then draw some points
> on top of the line, so I try something like
>
>  plot(x_line, y_line, ...)
>  scatter(x_point, y_point)
>
> but in the resulting plot it seems the points are
> drawn first and the lines drawn over them (so they are
> obscured).
>
> How do I specify the order in which the drawing should
> take place?
>
> thanks,
>
> a
>
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam?  Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
>
> -------------------------------------------------------------------------
> 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=3Dlnk&kid=3D120709&bid=3D263057&dat=
=3D121642
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

Hi,

I would like to draw a line, and then draw some points
on top of the line, so I try something like

 plot(x_line, y_line, ...)
 scatter(x_point, y_point)

but in the resulting plot it seems the points are
drawn first and the lines drawn over them (so they are
obscured).

How do I specify the order in which the drawing should
take place?

thanks,

a



__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com 

On Tuesday 11 July 2006 11:03, Andrew Straw wrote:
> Darren Dale wrote:
> > On Tuesday 11 July 2006 01:22, Andrew Straw wrote:
> >> Darren Dale wrote:
> >>> Hi Andrew,
> >>>
> >>> On Monday 10 July 2006 8:19 pm, Andrew Straw wrote:
> >>>> Where should I start trying to debug an issue where Adobe Illustrator
> >>>> CS for Windows is unable to open my EPS file generated by matplotlib?
> >>>> When attempting to open the file, a a dialog pops up that says, "The
> >>>> operation cannot complete because of an unknown error." So much for
> >>>> informative error messages. Ghostview 3.6.1 can read the file just
> >>>> fine, and Acrobat Distiller 7.0 for windows can also convert it to a
> >>>> PDF just fine. FWIW, I'm using matplotlib.rc('ps',usedistiller=None),
> >>>> but I get similar problems setting usedistiller='xpdf'.
> >>>>
> >>>> I'm basically an EPS file newbie, so don't be afraid to give me the
> >>>> equivalent of "did you make sure the power switch is turned on".
> >>>
> >>> I have a feeling its a problem with the font handling. I cant open a
> >>> file in inkscape either, the image looks fine but the fonts are
> >>> missing. Try setting ps.usedistiller = ghostscript. That converts the
> >>> file to low-level postscript, which CS should definitely be able to
> >>> open. It worked for inkscape, at least.
> >>
> >> Hi Darren,
> >>
> >> Hmm, that didn't do it.
> >
> > That is really surprising to me. How is it that Inkscape can open a
> > postscript file and Adobe's own software can not?
>
> Well, I didn't try Inkscape on it. My version of Inkscape doesn't seem
> to import EPS files. How are you doing it. I've tried pstoedit to
> convert it to SVG, but there were visible artifacts.

I'm using version 0.44

Darren Dale wrote:
> On Tuesday 11 July 2006 01:22, Andrew Straw wrote:
>   
>> Darren Dale wrote:
>>     
>>> Hi Andrew,
>>>
>>> On Monday 10 July 2006 8:19 pm, Andrew Straw wrote:
>>>       
>>>> Where should I start trying to debug an issue where Adobe Illustrator CS
>>>> for Windows is unable to open my EPS file generated by matplotlib? When
>>>> attempting to open the file, a a dialog pops up that says, "The
>>>> operation cannot complete because of an unknown error." So much for
>>>> informative error messages. Ghostview 3.6.1 can read the file just fine,
>>>> and Acrobat Distiller 7.0 for windows can also convert it to a PDF just
>>>> fine. FWIW, I'm using matplotlib.rc('ps',usedistiller=None), but I get
>>>> similar problems setting usedistiller='xpdf'.
>>>>
>>>> I'm basically an EPS file newbie, so don't be afraid to give me the
>>>> equivalent of "did you make sure the power switch is turned on".
>>>>         
>>> I have a feeling its a problem with the font handling. I cant open a file
>>> in inkscape either, the image looks fine but the fonts are missing. Try
>>> setting ps.usedistiller = ghostscript. That converts the file to
>>> low-level postscript, which CS should definitely be able to open. It
>>> worked for inkscape, at least.
>>>       
>> Hi Darren,
>>
>> Hmm, that didn't do it. 
>>     
>
> That is really surprising to me. How is it that Inkscape can open a postscript 
> file and Adobe's own software can not?
>
>   
Well, I didn't try Inkscape on it. My version of Inkscape doesn't seem
to import EPS files. How are you doing it. I've tried pstoedit to
convert it to SVG, but there were visible artifacts.
>> Simple plots (like simple_plot.py) work with no 
>> distiller step, so it must be something about my more complex plot.
>> Unfortunately, it's a rather complex menagerie of code that produces the
>> plot so I'm afraid that if I want to narrow this down, it'll be rather
>> painful and slow going. I might just stick with the
>> MPL->EPS->Distiller->PDF->Illustrator toolchain, which seems to work for
>> the moment.
>>     
>
> If you get time, you might edit the postscript file by hand and comment out 
> large sections of the code, and try importing those modified files.
>   

That's a good idea. I think I'll try it.

Some change have been introduce in matplotlib? Because I used this sequence=
=20
before and it was working. I'm a little bit surprise by the fact that the r=
gb=20
sequence must be three numbers between 0 and 1. Generally rgb sequence are=
=20
between 0 and 255, aren't they?


http://homepage.mac.com/jakesan/DHP/page0/page3/page3.html

And so my sequence is correct in this definition but yes false in the actua=
l=20
matplotlib definition but in this case an explicit error message must be=20
given to tell that RGB color doesn't respect the general convention and mus=
t=20
be between 0 and 1=20

Regards,

N.

Le mardi 11 juillet 2006 04:43, Eric Firing a =E9crit=A0:
> An rgb colorspec in matplotlib must be a sequence of three numbers
> between zero and one, so the problem is that you are indeed giving an
> invalid rgb arg.
>
> I think perhaps you grabbed an error message from a different instance
> of this error; when I try it, I get an error message that correctly
> gives the invalid arg that was supplied:
>
> ValueError: to_rgb: Invalid rgb arg "(120, 120, 120)"
> to_rgb: Invalid rgb arg "(120, 120, 120)"
>
>
> Eric
>
> hu...@ya... wrote:
> > 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 =3D pylab.plot([1,2],[2,3],'o')
> > pylab.setp(p,markerfacecolor=3D(120,120,120),markersize=3D5,markeredgew=
idth=3D1
> >.,zorder=3D50)
> >
> > 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.
> >
> >
> > -----------------------------------------------------------------------=
=2D-
> > Using Tomcat but need to do more? Need to support web services, securit=
y?
> > 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=3Dlnk&kid=3D120709&bid=3D263057&dat=
=3D121642
> > _______________________________________________
> > Matplotlib-users mailing list
> > Mat...@li...
> > https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>
> -------------------------------------------------------------------------
> 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=3Dlnk&kid=3D120709&bid=3D263057&dat=
=3D121642
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

On Tuesday 11 July 2006 01:22, Andrew Straw wrote:
> Darren Dale wrote:
> > Hi Andrew,
> >
> > On Monday 10 July 2006 8:19 pm, Andrew Straw wrote:
> >> Where should I start trying to debug an issue where Adobe Illustrator CS
> >> for Windows is unable to open my EPS file generated by matplotlib? When
> >> attempting to open the file, a a dialog pops up that says, "The
> >> operation cannot complete because of an unknown error." So much for
> >> informative error messages. Ghostview 3.6.1 can read the file just fine,
> >> and Acrobat Distiller 7.0 for windows can also convert it to a PDF just
> >> fine. FWIW, I'm using matplotlib.rc('ps',usedistiller=None), but I get
> >> similar problems setting usedistiller='xpdf'.
> >>
> >> I'm basically an EPS file newbie, so don't be afraid to give me the
> >> equivalent of "did you make sure the power switch is turned on".
> >
> > I have a feeling its a problem with the font handling. I cant open a file
> > in inkscape either, the image looks fine but the fonts are missing. Try
> > setting ps.usedistiller = ghostscript. That converts the file to
> > low-level postscript, which CS should definitely be able to open. It
> > worked for inkscape, at least.
>
> Hi Darren,
>
> Hmm, that didn't do it. 

That is really surprising to me. How is it that Inkscape can open a postscript 
file and Adobe's own software can not?

> Simple plots (like simple_plot.py) work with no 
> distiller step, so it must be something about my more complex plot.
> Unfortunately, it's a rather complex menagerie of code that produces the
> plot so I'm afraid that if I want to narrow this down, it'll be rather
> painful and slow going. I might just stick with the
> MPL->EPS->Distiller->PDF->Illustrator toolchain, which seems to work for
> the moment.

If you get time, you might edit the postscript file by hand and comment out 
large sections of the code, and try importing those modified files.

Dear All,

i was wondering if they are a binary package for matplotlib for 
macos10.3 with python2.4, and the last version of numpy. The one i 
found is only the 0.82 and required numeric.
Or do i have to build from source.

I am a bit confused as the last source file still talk about numeric 
and numarray.

Thanks for your help

Brice

On this topic, here is something I used the other day (just some 
different dash sequences):

e, = plot(x, y, 'k', label=r'$\theta_3=%1.2f$'%(th3))
setp(e, dashes={0:(1,0), 1:(2,2), 2:(10,4), 3:(10,4,4,4), 4:(10,2,2,2), 
5:(15,2,6,2)}[i])

Maybe we should just blatantly copy the gnuplot sequence, although the 
sequence might be gpl'ed!
One question which arises is that it wasn't clear what to set dashes to 
to get a solid line. I ended up doing the 0: case above i.e. (1,0), but 
I suspect this isn't ideal because it might generate lots of unwanted 
line segments. I think I tried None and (1) and it didn't work. Perhaps 
(999,0) would be better?

Gary R.

An rgb colorspec in matplotlib must be a sequence of three numbers 
between zero and one, so the problem is that you are indeed giving an 
invalid rgb arg.

I think perhaps you grabbed an error message from a different instance 
of this error; when I try it, I get an error message that correctly 
gives the invalid arg that was supplied:

ValueError: to_rgb: Invalid rgb arg "(120, 120, 120)"
to_rgb: Invalid rgb arg "(120, 120, 120)"


Eric

hu...@ya... wrote:
> 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.
> 
> 
> -------------------------------------------------------------------------
> 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 Dale wrote:
> Hi Andrew,
>
> On Monday 10 July 2006 8:19 pm, Andrew Straw wrote:
>   
>> Where should I start trying to debug an issue where Adobe Illustrator CS
>> for Windows is unable to open my EPS file generated by matplotlib? When
>> attempting to open the file, a a dialog pops up that says, "The
>> operation cannot complete because of an unknown error." So much for
>> informative error messages. Ghostview 3.6.1 can read the file just fine,
>> and Acrobat Distiller 7.0 for windows can also convert it to a PDF just
>> fine. FWIW, I'm using matplotlib.rc('ps',usedistiller=None), but I get
>> similar problems setting usedistiller='xpdf'.
>>
>> I'm basically an EPS file newbie, so don't be afraid to give me the
>> equivalent of "did you make sure the power switch is turned on".
>>     
>
> I have a feeling its a problem with the font handling. I cant open a file in 
> inkscape either, the image looks fine but the fonts are missing. Try setting 
> ps.usedistiller = ghostscript. That converts the file to low-level 
> postscript, which CS should definitely be able to open. It worked for 
> inkscape, at least.
>   
Hi Darren,

Hmm, that didn't do it. Simple plots (like simple_plot.py) work with no
distiller step, so it must be something about my more complex plot.
Unfortunately, it's a rather complex menagerie of code that produces the
plot so I'm afraid that if I want to narrow this down, it'll be rather
painful and slow going. I might just stick with the
MPL->EPS->Distiller->PDF->Illustrator toolchain, which seems to work for
the moment.

>>>>> "Fernando" == Fernando Perez <fpe...@gm...> writes:

    Fernando> Hi all, this is somewhat of a half-feature request,
    Fernando> half-question.  I just went through a rather unpleasant
    Fernando> exercise in trying to get a line plot with about 8
    Fernando> traces generated for black and white printing.  As it
    Fernando> turns out, mpl seems to only have 4 line styles ('-',
    Fernando> '--', '-.', ':'), which isn't really a whole lot
    Fernando> (compare this to gnuplot's extensive dashing support).

Are you aware of the "dashes" property, which allows you to set the
exact dash pattern you want.  It's an arbitrary length sequence of
alternating ink-on, ink-off, in points

# 5 points on, 2 off, 10 on, 5 off)
plot(arange(20), '--', dashes=[5,2,10,5])

    Fernando> Additionally, I'd like to suggest having a b/w mode,
    Fernando> where mpl's auto-selection of different colors for
    Fernando> successive line plots becomes a rotation of dashing
    Fernando> modes.  Gnuplot's EPS backend has exactly this feature,

This seems like a good idea -- if you define a nice sequence of dashes
you want to cycle through, I'll build the rest of the infrastructure
and make a figure property like iscolor.

JDH

Hi Andrew,

On Monday 10 July 2006 8:19 pm, Andrew Straw wrote:
> Where should I start trying to debug an issue where Adobe Illustrator CS
> for Windows is unable to open my EPS file generated by matplotlib? When
> attempting to open the file, a a dialog pops up that says, "The
> operation cannot complete because of an unknown error." So much for
> informative error messages. Ghostview 3.6.1 can read the file just fine,
> and Acrobat Distiller 7.0 for windows can also convert it to a PDF just
> fine. FWIW, I'm using matplotlib.rc('ps',usedistiller=None), but I get
> similar problems setting usedistiller='xpdf'.
>
> I'm basically an EPS file newbie, so don't be afraid to give me the
> equivalent of "did you make sure the power switch is turned on".

I have a feeling its a problem with the font handling. I cant open a file in 
inkscape either, the image looks fine but the fonts are missing. Try setting 
ps.usedistiller = ghostscript. That converts the file to low-level 
postscript, which CS should definitely be able to open. It worked for 
inkscape, at least.

Darren

Hi all,

this is somewhat of a half-feature request, half-question.  I just
went through a rather unpleasant exercise in trying to get a line plot
with about 8 traces generated for black and white printing.  As it
turns out, mpl seems to only have 4 line styles ('-', '--', '-.',
':'), which isn't really a whole lot (compare this to gnuplot's
extensive dashing support).  One can combine dashing with markers, but
the results aren't really very pretty (the relationship in spacing
between the dashing and the markers causes this, since the markers are
right at the data points while the dashing is whatever it is).

Mpl's color support is outstanding, but I need these figures in b/w
for a paper that will have no color figures, and I'm wondering what
others have resorted to in similar situations.

Additionally, I'd like to suggest having a b/w mode, where mpl's
auto-selection of different colors for successive line plots becomes a
rotation of dashing modes.  Gnuplot's EPS backend has exactly this
feature, and it's absolutely fantastic: if color is on, it
auto-selects amongst many colors, but if color is off, it
automatically switches to contrasting dashing modes.  This more or
less ensures that you can get the same plot made, either in color or
b/w, with nearly zero effort and still have distinguishable traces.
It's really nice to be able to generate a color version of the figures
for a talk and a b/w one for a paper, without hours of manual tweaks.

Anyway, I hacked an ugly-but-functional solution on my own, so this
message is mostly to put the issue on the radar, though I /am/
interested in solutions others may have.

Cheers,

f

Where should I start trying to debug an issue where Adobe Illustrator CS
for Windows is unable to open my EPS file generated by matplotlib? When
attempting to open the file, a a dialog pops up that says, "The
operation cannot complete because of an unknown error." So much for
informative error messages. Ghostview 3.6.1 can read the file just fine,
and Acrobat Distiller 7.0 for windows can also convert it to a PDF just
fine. FWIW, I'm using matplotlib.rc('ps',usedistiller=None), but I get
similar problems setting usedistiller='xpdf'.

I'm basically an EPS file newbie, so don't be afraid to give me the
equivalent of "did you make sure the power switch is turned on".

Cheers!
Andrew

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