matplotlib

Hi,

I am a new user of matplotlib.
First of all I would like to say that the people working on matplotlib is
doing a great job.

Well, I have tried to use the 'fill', but I cannot get rid of the lines.
I have tried to use 'linewidth=0' at the end, but it did not work.

Could somebody, please, tell me if I am doing something wrong ?

Thank you.
Sergio.

------------------------------------------------------------------

#!/usr/bin/env python

from pylab import *
from matplotlib.patches import Polygon

t = arange(0.0, 1.0+0.01, 0.01)
s1 = t
s2 = t*t
s3 = t*t*t

text(0.50, 0.4,
     r"$d(f_2,f_3)$", horizontalalignment='center',
     color= '#8f0100', fontsize=30)

xticks(size=20)
yticks(size=20)

fill(t, s3, '#e9ccce', linewidth=0)
fill(t, s2, 'w', linewidth=0)

savefig('diamxn2.eps')

Sergio,
I think the line you see comes from plotting two shape on top one another. You 
may want to redefine your polygon:
the easier would be something like:

tt = concatenate((t,t[::-1]))
vtx = concatenate((s3,s2[::-1]))
fill(tt, vtx, '#e9ccce', linewidth=0)

With the first command, you build a series of x coordinates from 0 to 1.01 and 
back to 0 (that's the t[::-1])
with second, you build the y ccordinates sequence, by taking the corresponindg 
point of s3, and then from s2 in reverse order. 
Now, your polygon is fully defined.

>>>>> "Sergio" == Sergio Drumond Ventura <damxtha@...> writes:

    Sergio> Hi, I am a new user of matplotlib.  First of all I would
    Sergio> like to say that the people working on matplotlib is doing
    Sergio> a great job.

    Sergio> Well, I have tried to use the 'fill', but I cannot get rid
    Sergio> of the lines.  I have tried to use 'linewidth=0' at the
    Sergio> end, but it did not work.

    Sergio> Could somebody, please, tell me if I am doing something
    Sergio> wrong ?


Whether or not linewidth=0 is respected may be backend dependent.  In
postscript it means use the smallest possible line.  We have discussed
overriding this at the mpl level to impose consistency, but am not
sure what the status of this is.  The safest best is to set the
edgecolor and facecolor to be identical.

JDH

John Hunter wrote:

> Whether or not linewidth=0 is respected may be backend dependent.  In
> postscript it means use the smallest possible line.  We have discussed
> overriding this at the mpl level to impose consistency, but am not
> sure what the status of this is.  The safest best is to set the
> edgecolor and facecolor to be identical.

John,

We did decide to make linewidth=0 suppress drawing the line, and this is 
in the ps backend.  Most likely it is not in all backends, but it is in 
pdf, svg, and agg as well as ps.  In the ps backend it is in the 
_draw_ps() method, so unless there is a code path that does not use this 
method, it should work.

Sergio, I deleted your original message so I don't remember how much 
info you gave.  If linewidth=0 is not suppressing edge drawing and you 
are using mpl 0.87.7 or svn, then please provide a simple script 
illustrating the problem and say what backend and mpl version you are using.

Eric

>>>>> "Eric" == Eric Firing <efiring@...> writes:
    Eric> We did decide to make linewidth=0 suppress drawing the line,
    Eric> and this is in the ps backend.  Most likely it is not in all
    Eric> backends, but it is in pdf, svg, and agg as well as ps.  In

Would it not be better to catch this at the Artist level and either
not make a call to the backend, or force the edgecolor=facecolor
before calling the backend?  Then the backend can remain blissfully
ignorant...

JDH

John Hunter wrote:
>>>>>> "Eric" == Eric Firing <efiring@...> writes:
>     Eric> We did decide to make linewidth=0 suppress drawing the line,
>     Eric> and this is in the ps backend.  Most likely it is not in all
>     Eric> backends, but it is in pdf, svg, and agg as well as ps.  In
> 
> Would it not be better to catch this at the Artist level and either
> not make a call to the backend, or force the edgecolor=facecolor
> before calling the backend?  Then the backend can remain blissfully
> ignorant...

No, this strategy won't work for two reasons:

1) edgecolor=facecolor is not the same as not drawing the edge; it leads 
to artifacts that can be very damaging.

2) the backends implement patch rendering which inherently includes both 
the edge and the fill, so we can't avoid having mechanisms for telling 
the backend whether to stroke the former and/or paint the latter.

Eric

> 
> JDH

On Tue, 26 Dec 2006, Eric Firing apparently wrote: 
> 1) edgecolor=facecolor is not the same as not drawing the 
> edge; it leads to artifacts that can be very damaging. 

Strongly agree!

Cheers,
Alan Isaac