matplotlib-users

[Matplotlib-users] y label positioning

[Jeff P. <jef...@se...>]

Hello, I don't know if my last email was posted so I'll try again. Is
there a way to position a y axis label?  By default it seems to be
placed directly over the y-axis tick marks and looks really bad. Thanks.

Jeff

Re: [Matplotlib-users] y label positioning

[John H. <jdh...@ac...>]

>>>>> "Jeff" == Jeff Peery <jef...@se...> writes:

    Jeff> Hello, I don't know if my last email was posted so I'll try
    Jeff> again. Is there a way to position a y axis label?  By
    Jeff> default it seems to be placed directly over the y-axis tick
    Jeff> marks and looks really bad. Thanks.

Could you post a script that replicates your problem, and possibly an
image.  Also the result of running your script with --verbose-helpful.

Thanks,
JDH

RE: [Matplotlib-users] y label positioning

[Jeff P. <jef...@se...>]

Hi, yes I attached an image and a piece of my script (frame2.py). What
do you think? Thanks.



-----Original Message-----
From: John Hunter [mailto:jdh...@ni...] 
Sent: Wednesday, May 25, 2005 9:56 AM
To: Jeff Peery
Cc: mat...@li...
Subject: Re: [Matplotlib-users] y label positioning

>>>>> "Jeff" == Jeff Peery <jef...@se...> writes:

    Jeff> Hello, I don't know if my last email was posted so I'll try
    Jeff> again. Is there a way to position a y axis label?  By
    Jeff> default it seems to be placed directly over the y-axis tick
    Jeff> marks and looks really bad. Thanks.

Could you post a script that replicates your problem, and possibly an
image.  Also the result of running your script with --verbose-helpful.

Thanks,
JDH

Re: [Matplotlib-users] y label positioning

[John H. <jdh...@ac...>]

>>>>> "Jeff" == Jeff Peery <jef...@se...> writes:

    Jeff> Hi, yes I attached an image and a piece of my script
    Jeff> (frame2.py). What do you think? Thanks.

I see.  This looks like a WX bug -- could you file a sourceforge bug
report and include your two files you attached?  


Is there a reason you are not using WXAgg?  This will probably fix
this problem for you and make nicer figures too..

import matplotlib
matplotlib.use('WXAgg')
from matplotlib.backends.backend_wxagg import FigureCanvasWxAgg as FigureCanvas
from matplotlib.backends.backend_wx import NavigationToolbar2Wx

JDH 

RE: [Matplotlib-users] y label positioning

[Jeff P. <jef...@se...>]

Thanks John,

Well I don't know why I'm not using WXAgg, I'm fairly new to this
matplotlib stuff. I'm using wxpython, will wxAgg work with this? Thanks.

Jeff

-----Original Message-----
From: John Hunter [mailto:jdh...@ni...] 
Sent: Wednesday, May 25, 2005 11:43 AM
To: Jeff Peery
Cc: mat...@li...
Subject: Re: [Matplotlib-users] y label positioning

>>>>> "Jeff" == Jeff Peery <jef...@se...> writes:

    Jeff> Hi, yes I attached an image and a piece of my script
    Jeff> (frame2.py). What do you think? Thanks.

I see.  This looks like a WX bug -- could you file a sourceforge bug
report and include your two files you attached?  


Is there a reason you are not using WXAgg?  This will probably fix
this problem for you and make nicer figures too..

import matplotlib
matplotlib.use('WXAgg')
from matplotlib.backends.backend_wxagg import FigureCanvasWxAgg as
FigureCanvas
from matplotlib.backends.backend_wx import NavigationToolbar2Wx

JDH 

Re: [Matplotlib-users] y label positioning

[John H. <jdh...@ac...>]

>>>>> "Jeff" == Jeff Peery <jef...@se...> writes:

    Jeff> Thanks John, Well I don't know why I'm not using WXAgg, I'm
    Jeff> fairly new to this matplotlib stuff. I'm using wxpython,
    Jeff> will wxAgg work with this? Thanks.

Yes, the wx backend is something of a historical artifact.  Around
matplotlib-0.50, Perry Greenfield suggested using the antigrain
library as a core image renderer, and transfer this image into the
respective graphical user interfaces.  This idea came from Eric Jones
and Chaco.  This simplifies development enormously because we don't
have to deal with the idiosyncrasies of all the GUI drawing
libraries.  

The WXAgg backend in general will look a lot better and have more
features than the plain vanilla wx backend.  It is slower than we
would like it to be, because we are not using the most efficient
method to transfer the agg canvas to wx, and it doesn't have all the
save formats as wx does.  For example, I noticed your attached image
was jpg.  wxagg doesn't support jpeg, but uses png instead.  This is a
good thing.  You will be much happier with your wxagg png images than
you are with wx jpeg images I suspect.

JDH