matplotlib-users Mailing List for matplotlib

On Wednesday 08 June 2005 17:12, John Hunter wrote:
> >>>>> "Nicolas" == Nicolas Girard <nic...@ne...> writes:
>
> Nicolas> Hi all, I find ytitle() to behave quite strangely ; the
> Nicolas> first link points to a figure to each left subplot of
> Nicolas> which I used
>
> Nicolas> ylabel(labl)
>
> Nicolas> and on the figure pointed by the second link I used
>
> Nicolas> text(-0.07,0.5,labl,verticalalignment='center',
> Nicolas> rotation='vertical',transform=gca().transAxes,clip_on=False)
>
>
> Nicolas> http://nicolasgirard.nerim.net/ytitle.jpg
> Nicolas> http://nicolasgirard.nerim.net/text.jpg
>
>
> Nicolas> from these 2 samples it seems like ytitle()'s behaviour
> Nicolas> is odd, or at least not optimal. What do you think ?
>
Sorry for the late answer.
> Which backend are you using? It could be a backend specific bug. 
I tried with the standard one (Agg ?), then I saved the plot as ps, png and 
jpeg ; and the result was the same
> From 
> the fact that you are making jpg images, my guess is you are using GTK
> or WX. 
Actually my concern was to produce files with reasonable size so that you can 
download them more quickly
> Unless you have good reason not to, I would advise you to use 
> GTKAgg/WXAgg and output PNG. PNG is a much better format for line art
> and text.
You must be right ; And the nice thing I've just discovered is that the png 
files are lighter than the jpeg ones... fine !
>
> Do you see the extra horizontal space in *Agg or PS backends? 
Yes
> Note 
> also that the space between the yticklabels and the ylabel is
> controlled by ax.yaxis.LABELPAD, which defaults to 5 points. 
The extra space is less problematic than the misalignment of the labels, in 
fact. As they get properly aligned with the text() function, I guess there's 
room for improvement without too much effort (at least I hope so)
> Also, 
> are you using mathtext or rc.usetex=True?
Yes, I have added "rc.usetex=True" to my config file
>
> When reporting problems, it is very helpful to
>
> 1) run your script with --verbose-helpful and report the output
>
Okay, here you are:
python t.py --verbose-helpful
matplotlib data path /usr/share/matplotlib
loaded rc file /home/ngirard/.matplotlibrc
matplotlib version 0.81
verbose.level helpful
interactive is False
platform is linux2
numerix Numeric 23.1
font search path ['/usr/share/matplotlib']
loaded ttfcache file /home/ngirard/.ttffont.cache
backend GTKAgg version 2.6.2
> 2) indicated any nondefault rc options (rc.usetex?)
Please find attached my config file.
>
> 3) attach a standalone script we can run, if possible
>
I've attached the script, but I'm afraid you can't run it, as it reads a huge 
data file I cannot send to you...
There's an other annoying bug with this script. For the subplots on columns 2 
and 3 I asked the yaxis to have only but 3 ticks, using:
 majorLocator = LinearLocator(numticks=3)
 ...
 a=subplot(nbvals,3,i)
 a.yaxis.set_major_locator(majorLocator)
which works, but as the figure gets refreshed, the ticks disappear, and at the 
end only part of them remain visible. I've encounetered this with the 
standard Agg backend, with either interactive and non-interactive mode. 
Saving as jpeg, png and ps didn't help, as you can see here:
http://nicolasgirard.nerim.net/out.png
Cheers,
Nicolas

I'm getting a "crash" when using ipython and pylab on WinXP.
The problem shows up when I have a subplot and try to use ylim to
change the axis scale. Here's an example (after plotting some data).
In [2]: ylim()
Out[2]: (0.0, 30000000000.0)
In [3]: xlim(-6, 6)
Out[3]: (-6, 6)
(axis scsale changes as expected)
In [4]: ylim(0, 1000)
( crash - i.e., CPU use goes to 100%, prompt does not return, Tkinter
and ipython windows unresponsive)
I just upgraded to pylab 0.81 (python 2.3.3) and see the same problem.
 I'm not sure how to debug this from python since I don't have a
prompt. I did add some print statements to my original script and it
seems all commands execute in non-interactive mode until p.show(). If
I comment out the ylim() command the script works as expected.
-- David

Hi all,
 rc('l',lw=1,mew=0,markersize=1)
gives:
 29 # save state (John, is there a cleaner way to do this?)
 30 rcsave = rcParams.copy()
---> 31 rc('l',lw=1,mew=0,markersize=1)
 32 ax.plot(x,y,marker)
 33 rcParams.update(rcsave)
/usr/lib/python2.3/site-packages/matplotlib/pylab.py in rc(*args, **kwargs)
 946
 947 def rc(*args, **kwargs):
--> 948 matplotlib.rc(*args, **kwargs)
 949 if matplotlib.rc.__doc__ is not None:
 950 rc.__doc__ = matplotlib.rc.__doc__
/usr/lib/python2.3/site-packages/matplotlib/__init__.py in rc(group, **kwargs)
 762 key = '%s.%s' % (group, name)
 763 if not rcParams.has_key(key):
--> 764 raise KeyError('Unrecognized key "%s" for group "%s" and 
name "%s"' %
 765 (key, group, name))
 766
KeyError: 'Unrecognized key "l.linewidth" for group "l" and name "linewidth"'
If I change 'l' to 'lines', it works. But the docs for rc() say that 'l' is a 
valid alias for lines.
Cheers,
f