matplotlib-users Mailing List for matplotlib

Arnd> P.S.: BTW: splattering the prints around seems like 
Arnd> poor-mans debugging ;-) Are there better solutions 
Arnd> available? 

The logging module allows you to use essentially the same 
strategy with a finer level of control.

fwiw,
Alan Isaac

>>>>> "Arnd" == Arnd Baecker <arn...@we...> writes:
    Arnd> I think the expression is alright: I looked at
    Arnd> matplotlib/text.py - class Text. It seems that for this
    Arnd> example the routine does not pass by the first use of
    Arnd> self._rgxsuper:


It looks like you're right -- good catch.  It should read

            if ismath=='TeX': m = None
            else: m = self._rgxsuper.match(self._text)
            if m is not None:
                bbox, info = self._get_layout_super(self._renderer, m)

    Arnd> P.S.: BTW: splattering the prints around seems like
    Arnd> poor-mans debugging ;-) Are there better solutions
    Arnd> available?

It is certainly poor-man's debugging, but it is a time honored
tradition that has served me well.  Of course, you could use the
python debugger, and it sometimes helps to embed an ipython shell in
the code

  from IPython.Shell import IPShellEmbed
  ipshell = IPShellEmbed()
  ipshell() # this call anywhere in your program will start IPython 


If you place this inside a function, a shell will pop up with the
local namespace which you can then inspect.

JDH

On Sat, 3 Sep 2005, Darren Dale apparently wrote: 
> I have wondered why the origin of the bbox was shifted in 
> eps files, but it shouldn't matter.

I agree is should not matter.  But it does for GhostScript's 
pdfwrite.

> Seeing as how dvips, ps2pdf, and epstopdf all work as 
> expected, it sounds like a dvipdfm bug to me. 

If it is a bug (and I also believe it is), it's a pdfwrite 
bug, assuming that pdfwrite should know how to produce 
encapsulated PDF, which has been treated as the case by many 
people for many years.

> 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. 

As you said, it should not matter.
And it will make pdfwrite work as expected.

Cheers,
Alan Isaac

Hi John,

On Sat, 3 Sep 2005, John Hunter wrote:

> >>>>> "arnd" == arnd baecker <arn...@we...> writes:
>     arnd> the y-axis has a different font (italic) than the x-axis
>     arnd> (sans-serif).  Looking at the code, this is because it is
>     arnd> set as math text ($ ...$).  Is there a trick to ensure a
>     arnd> sans-serif font for the y-axis?  (I would like to use
>     arnd> matplotlib plots in a presentation and sans-serif fonts are
>     arnd> better suited for this.)
>
> What version of mpl are you using?  I thought in a previous post you
> said you were using cvs (could be mistaken).

You remember the version I am running better than I do ;-).
In [1]: import matplotlib
In [2]: matplotlib.__version__
Out[2]: '0.84.cvs.2'

> I wrote an extension to
> text.py to special case exponential formatting specifically to solve
> the mismatched fonts problem.  So make sure you are using a current
> problem of matplotlib and if you still have the problem check your
> input against the regex in matplotlib.text.Text
>
>     # special case superscripting to speedup logplots
>     _rgxsuper = re.compile('\$([\-+0-9]+)\^\{(-?[0-9]+)\}\$')
>
> If you can fix up this expression to include your case that would be
> most helpful.

I think the expression is alright:
I looked at matplotlib/text.py - class Text. It seems that
for this example the routine does not pass by the
first use of self._rgxsuper:


	print "Arriving here1"
        if angle==0:
	    print "Arriving here2"
            if ismath!='TeX':            # <==== change to "==" here?
		print "Arriving here3"
 		m = None
            else:
                m = self._rgxsuper.match(self._text)
		print "passing by here..."
	    print "Arriving here4"
            if m is not None and not rcParams['text.usetex']:
		print "Arriving here5"
                bbox, info = self._get_layout_super(self._renderer, m)
                base, xt, yt = info[0]
                renderer.draw_text(gc, xt, yt, base,
                                   self._fontproperties, angle,
                                   ismath=False)

                exponent, xt, yt, fp = info[1]
                renderer.draw_text(gc, xt, yt, exponent,
                                   fp, angle,
                                   ismath=False)
                return

However, changing ismath!='TeX' to ismath=='TeX'
seems to work (for this particular example): I.e. I get
the non-math fonts on the vertical axis.
Can you confirm that this change is the correct solution?

Best,

Arnd

P.S.: BTW: splattering the prints around seems like poor-mans
debugging ;-) Are there better solutions available?

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

What version of mpl are you using?  I thought in a previous post you
said you were using cvs (could be mistaken).  I wrote an extension to
text.py to special case exponential formatting specifically to solve
the mismatched fonts problem.  So make sure you are using a current
problem of matplotlib and if you still have the problem check your
input against the regex in matplotlib.text.Text

    # special case superscripting to speedup logplots
    _rgxsuper = re.compile('\$([\-+0-9]+)\^\{(-?[0-9]+)\}\$')

If you can fix up this expression to include your case that would be
most helpful.

Thanks,
JDH