matplotlib-users Mailing List for matplotlib

Hi,

for this example

  from pylab import *
  x=arange(10)
  semilogy(x,1+x)

the y-axis has a different font (italic) than the x-axis (sans-serif).
Looking at the code, this is because it is set as math text ($ ...$).
Is there a trick to ensure a sans-serif font for the y-axis?
(I would like to use matplotlib plots in a presentation
and sans-serif fonts are better suited for this.)

Best,

Arnd

On Saturday 03 September 2005 1:14 am, Alan G Isaac wrote:
> On Fri, 2 Sep 2005, Darren Dale apparently wrote:
> > are you using a mac?
>
> No. I'm on a PC.  And although I in general understand
> John's request for a script, I think the EPS file I provided
> will be more helpful in pinning this down.  It took me
> a while to see it, but finally I got it.
>
> If you look at the bounding box, it is outside all standard
> paper sizes.  Now it turns out that pdfwrite assumes a paper
> size and clips outside that size.  Thus my figure did not
> show because it was clipped.  This does not happen when one
> uses dvips because the EPS file is handled *as* an EPS
> *before* creation of the PDF file.
>
> Lesson (I think): matplotlib should create its EPS files so
> that they have bounding boxes inside a4 width and letter
> paper height boundaries, or people will have trouble with
> their standard configurations of some standard tools.

I have wondered why the origin of the bbox was shifted in eps files, but it 
shouldn't matter. Seeing as how dvips, ps2pdf, and epstopdf all work as 
expected, it sounds like a dvipdfm bug to me. 

I don't think its a good idea to limit the size of eps figures. At some point, 
I will make eps files that are larger than A4 for use in posters.

Darren

> Thanks Sascha,
>
> The point of my reply was that others can benefit from what you've
> learned.  Even if you feel like you are a newbie, trust me, others
> will be glad to benefit from what you've learned.  So please send the
> information to the list.  I've forwarded your response.

It's been a pleasure. I actually intended to send my reply to the list and 
did not look at who I was really sending it to. Sorry again.

Sascha 

On Fri, 2 Sep 2005, Darren Dale apparently wrote: 
> are you using a mac? 

No. I'm on a PC.  And although I in general understand 
John's request for a script, I think the EPS file I provided 
will be more helpful in pinning this down.  It took me 
a while to see it, but finally I got it.

If you look at the bounding box, it is outside all standard 
paper sizes.  Now it turns out that pdfwrite assumes a paper 
size and clips outside that size.  Thus my figure did not 
show because it was clipped.  This does not happen when one
uses dvips because the EPS file is handled *as* an EPS 
*before* creation of the PDF file.

Lesson (I think): matplotlib should create its EPS files so 
that they have bounding boxes inside a4 width and letter 
paper height boundaries, or people will have trouble with 
their standard configurations of some standard tools.

Alan Isaac

PS I belive the matplotlib EPS files are written with 
a superfluous gsave (just search for 'gsave' and you'll find 
it in the file where it should not be), but this is not the 
source of my problem.

>  I could guess at what you are trying to do, but  =20
> it would help a lot if  you posted an example =20
> that we could run, with  comments about what you  =20
> want to happen versus what is happening.

thanks... attached is an image of roughly what i =20
want.  a program is below.

#!/usr/bin/python
from pylab import *
N=3D20
def xycs():
  x,y=3Dresize(rand(2*N),(2,N))
  x[:N/2]*=3D2;y[:N/2]/=3D2;
  c=3Darray([0]*(N/2)+[1]*(N/2))
  s=3Darray(([400]+[30]*(N/2-1))*2)
  print zip(c,s)
  p=3Dscatter(x,y,c=3Dc,s=3Ds,faceted=3D0)
  grid(True)
  setp(p, 'alpha', 0.75)
  savefig('scat_lgnd.png')
  show()
  return 0
if __name__=3D=3D'__main__':
  xycs()

I will be out of the office until September 26.  I will respond to your message as soon as I return.

Thank you,

Eli

>>>>> "Alan" == Alan Isaac <ai...@am...> writes:

    Alan> On Fri, 02 Sep 2005, John Hunter wrote:
    >> If you could send a docstring patch, that would be great.

    Alan> I was going to but I looked in pylab.py and found a note
    Alan> that the plot function def and docs were automatically
    Alan> generated, so I did not know what file to patch.  (Sorry;
    Alan> I'm new to this kind of thing.)

No problem.

pylab.py is for the most part a thin wrapper of functionality of
axes.py.  Eg, pylab.plot calls ax.plot and pylab.imshow calls
ax.imshow.  So if you find a problem with a pylab docstring, you can
usually find the original function in axes.py and fix that.

If you are on a win32 platform, which I think wyou are, you can install
ming32 and run a diff command like the one suggested by Charles Moad
at

  http://sourceforge.net/mailarchive/message.php?msg_id=12793726

If you are not comfortable with cvs/patch/diff, that's fine.  Just
edit the files in question and send them to me as an attachment and I
can deal with them.  

Thanks,
JDH

On Friday 02 September 2005 10:00 pm, John Hunter wrote:
> >>>>> "Alan" == Alan G Isaac <ai...@am...> writes:
>
>     Alan> My lovely matplotlib EPS graphics are missing in my PDF
>     Alan> files if I use dvipdfm.  It looks (?) like they are included
>     Alan> but then are blanked out afterwards.  Any idea why?  I have
>     Alan> never had trouble with other EPS files.
>
> We've seen a number of reports of problems in converting matplotlib
> eps files -> pdf.  To help us narrow the potential causes of the
> problem, could you provide the results of --verbose-helpful with an
> example script and rc file, as well as platform and version info for
> latex, gs, and otherwise.  Just give us as much information as you
> can, what sequence of commands you are issuing and what versions of
> each you are using.  Nonstandard rc settings (usetex?) and so on.
>
> matplotlib can be used in a lot of ways.  If you submit a script and
> an rc file (if it is different in any way than the default) and the
> commands you are typing and some extra version info, then it helps
> pare down the list of potential explanations for the problems you are
> seeing.

Alan, are you using a mac? If so, I wonder if this is related to embedding the 
native mac fonts. One user a while back reported having to change his font 
settings in matplotlibrc to load the bitstream fonts instead of the apple 
fonts. 

-- 
Darren S. Dale

Bard Hall
Department of Materials Science and Engineering
Cornell University
Ithaca, NY. 14850

dd...@co...
http://people.ccmr.cornell.edu/~dd55/

>>>>> "Jack" == Jack Andrews <ef...@iv...> writes:

    Jack> hi, i've been having lots of fun with scatter plots and
    Jack> coloured circles.  i want to provide a legend.

    Jack> i'm using colour to define discrete elements rather than
    Jack> continuous values (so colorbar() isn't much help to me -- i
    Jack> think...)

    Jack> basically: (red) chevrolet (orange) mazda (yellow) honda ...

    Jack> any tips?

I could guess at what you are trying to do, but it would help a lot if
you posted an example that we could run, with comments about what you
want to happen versus what is happening.

Have you seen examples/legend_demo2.py, which illustrates how to make
legends for a subset of objects in the plot?

JDH

>>>>> "Alan" == Alan G Isaac <ai...@am...> writes:

    Alan> My lovely matplotlib EPS graphics are missing in my PDF
    Alan> files if I use dvipdfm.  It looks (?) like they are included
    Alan> but then are blanked out afterwards.  Any idea why?  I have
    Alan> never had trouble with other EPS files.

We've seen a number of reports of problems in converting matplotlib
eps files -> pdf.  To help us narrow the potential causes of the
problem, could you provide the results of --verbose-helpful with an
example script and rc file, as well as platform and version info for
latex, gs, and otherwise.  Just give us as much information as you
can, what sequence of commands you are issuing and what versions of
each you are using.  Nonstandard rc settings (usetex?) and so on.

matplotlib can be used in a lot of ways.  If you submit a script and
an rc file (if it is different in any way than the default) and the
commands you are typing and some extra version info, then it helps
pare down the list of potential explanations for the problems you are
seeing.

Thanks,
JDH