matplotlib-users Mailing List for matplotlib (Page 3)

Hi,
Thank you for pointing that out, that does indeed do what I want
mostly. However, while the data is autoscaled to the plot, the values
on the y axis are not updated and they remain at their original
values. I suspect this is because I am not giving a command to redraw
the axes. How would I go about doing that? I think I need to blit a
larger bbox that encompasses the axes as well, but I'm not sure how to
get that.
By the way, I found that self.ax1.autoscale_view(scalex=False, scaley
= True) seems to autoscale just the y axis and seems clearer than the
set_ylim code suggested below.
Thanks again,
Glenn

On 4/26/08, John Hunter <jd...@gm...> wrote:
> On Fri, Apr 25, 2008 at 1:19 AM, G Jones <gle...@gm...> wrote:
>  > Hello,
>  >  Thank you for the suggestion. However, I am refering to the
>  >  canvas.restore_region, draw_artist, blit, gui_repaint sort of
>  >  animation.
>  >  Glenn
>
>
> His suggestion is still correct -- after you update the line data and
>  before you call draw_artist, you can acll relim and autoscale_view as
>  Mattias suggested.  However, this will not always do what you want,
>  because it will autoscale both the x and the y.  In animated plots,
>  often you are just updating the ydata an want to manually control the
>  xlim and autoscale the ylim (eg strip charting).  In that case, I
>  would do :
>
>         self.ax1.relim()
>         self.ax1.set_ylim(*self.ax1.yaxis.major.locator.autoscale())
>
>   JDH
>

Hello all,

Thanks again for all the help so far -- you guys are great! But presently I
have a (potentially silly) question. So I'm attempting to create a plot of
essentially two lists of data, but would like two x-axes: one along the top
in one length scale, another along the bottom in another length scale. I've
tried manually setting another x-axis at coordinates matching the top side
of the plot box, but that didn't work out so well:

    loglog(wavelength, flux, "ko")
    axis([1, 100, 10000, 1000000])
    a = axes([0.15, 0.95, 0.85, 0.01], frameon=False)
    a.yaxis.set_visible(False)
    a.set_xticklabels(["test1", "test2", "test3"])

(essentially I made another plot set into the larger one and moved it around
until the bottom/x-axis of that plot was along the top of the larger plot...
ugly tickmarks above the tickmark labels, though)

Then I tried the twinx() solution:

    ax1 = subplot(111)
    loglog(wavelength, flux, "ko")

    ax2 = twinx()
    ax2.xaxis.tick_top()
    ax2.set_xticklabels(["test1", "test2", "test3"])
    show()

Problem is, I change the labels of the second x-axis, it changes the labels
of the bottom one, too... I'm essentially trying to have two scales which
are functions of each other, one along the top and the other along the
bottom, but for the same dataset. I've tried scouring all sorts of
documentation and forums but haven't found quite what I'm looking for. Any
help would be much appreciated!

On Sat, Apr 19, 2008 at 9:07 AM, Yong-Duk Jin <ne...@gm...> wrote:
> When I increase the xlabel fontsize, it overlaps with the tick label.
> How can I adjust the distance between tick label and xlable (or ylabel)?
> Please help me.

This shouldn't happen if the font metrics are correct, since the label
gets the bounding box of the tick labels and adjusts itself correctly.
 What mpl version and backend are you using?

To increase the distance, you can increase the LABELPAD parameter

ax.xaxis.LABELPAD = 8  # default is 5

JDH

On Fri, Apr 25, 2008 at 1:19 AM, G Jones <gle...@gm...> wrote:
> Hello,
>  Thank you for the suggestion. However, I am refering to the
>  canvas.restore_region, draw_artist, blit, gui_repaint sort of
>  animation.
>  Glenn

His suggestion is still correct -- after you update the line data and
before you call draw_artist, you can acll relim and autoscale_view as
Mattias suggested.  However, this will not always do what you want,
because it will autoscale both the x and the y.  In animated plots,
often you are just updating the ydata an want to manually control the
xlim and autoscale the ylim (eg strip charting).  In that case, I
would do :

        self.ax1.relim()
        self.ax1.set_ylim(*self.ax1.yaxis.major.locator.autoscale())

 JDH

Hi Yong-Duk,

On Saturday 26 April 2008 08:26:33 am Yong-Duk Jin wrote:
> I tested saving in a 'eps' format function using the test code
> from http://www.scipy.org/Cookbook/Matplotlib/LaTeX_Examples.
>
> The code looks like
>
>
> #####################################################################
> import pylab
> from pylab import arange,pi,sin,cos,sqrt
> fig_width_pt = 246.0  # Get this from LaTeX using \showthe\columnwidth
> inches_per_pt = 1.0/72.27               # Convert pt to inch
> golden_mean = (sqrt(5)-1.0)/2.0         # Aesthetic ratio
> fig_width = fig_width_pt*inches_per_pt  # width in inches
> fig_height = fig_width*golden_mean      # height in inches
> fig_size =  [fig_width,fig_height]
> params = {'backend': 'ps',
>           'axes.labelsize': 10,
>           'text.fontsize': 10,
>           'legend.fontsize': 10,
>           'xtick.labelsize': 8,
>           'ytick.labelsize': 8,
>           'text.usetex': True,
>           'figure.figsize': fig_size}
> pylab.rcParams.update(params)
> # Generate data
> x = pylab.arange(-2*pi,2*pi,0.01)
> y1 = sin(x)
> y2 = cos(x)
> # Plot data
> pylab.figure(1)
> pylab.clf()
> pylab.axes([0.125,0.2,0.95-0.125,0.95-0.2])
> pylab.plot(x,y1,'g:',label='$\sin(x)$')
> pylab.plot(x,y2,'-b',label='$\cos(x)$')
> pylab.xlabel('$x$ (radians)')
> pylab.ylabel('$y$')
> pylab.legend()
> pylab.savefig('eps.eps')
> pylab.savefig('png.png',dpi=200)
> #####################################################################
>
> After trying the above code, I found 2 problems in saving in 'eps' format.
> I attached the result saved in eps format (eps.jpg) along with the result
> saved in png format (png.png) to describe the problems.
>
> 1. The location of axes is not correct when the plot is saved in 'eps'
> format. It seems like that the appointed axes location is ignored when any
> of the component in the plot is out of the figure.

That is the result of an unfortunate workaround we have to use with the latex 
backend. Briefly: the figure you are making is actually inserted into a latex 
document, in order for latex to render the text. Latex yields a postscript 
file, which does not include a bounding box. You want an eps file, with a 
bounding box that preserves the placement of your axes in the visible window, 
but the bbox is recalculated by ghostscript based on the contents of the 
image. I don't know how to improve this, aside from switching to Jouni's 
dviread.

> 2. Although the legend label in the 'eps' file is acceptable, the legend
>    label in 'png' file looks better.

They look about the same to me, and I don't know what you mean by better. I 
will say though, that there are better postscript viewers out there than the 
one you are using. The tick labels in your eps example do not look as good as 
they could. I see the same thing with kpdf, Adobe Reader does a better job of 
rendering the text in our figures than does kpdf.

> In addition to the above problems, I want to know whether there exists a
> way to
> adjust the distance between a axis label and tick label. When I raised the
> axis
> label font size to 11 or 12, the gap between a axis label and tick label
> becomes
> too small. I may be able to put a text instead of axis label, it, however,
> takes too
> much time for me to determine the proper text position manually everytime.
> Actually I've asked the same question few days ago and I've not no  answer
> so far.
> Aren't there any proper way to adjust the distance between a axis label and
> tick label?

I don't know.

Darren

Christopher Brown <c-...@as...> writes:

> With mpl 0.91.2, the markeredgewidth property does not seem to have an 
> effect when using the pdf backend (seems to always be 1, regardless of 
> what I set it to, and it seems to be fine with other backends). 

I can't replicate this problem. Could you send me (off-list) the
resulting pdf file and a screenshot from your pdf viewer?

-- 
Jouni K. Seppänen
http://www.iki.fi/jks

Hi List,

With mpl 0.91.2, the markeredgewidth property does not seem to have an 
effect when using the pdf backend (seems to always be 1, regardless of 
what I set it to, and it seems to be fine with other backends). Here is 
a minimal example:

from matplotlib import use
#use('pdf') # <- Uncomment for pdf

import matplotlib.pyplot as plt
hf=plt.plot([1,2],[1,1],marker='o',mfc='white', ms=12, mew=4, ls="None")
plt.xlim(.5,2.5)
plt.savefig("c:\\test")

-- 
Chris

John Hunter wrote:
> I may have spoken too quickly -- I forgot that on my system in order
> to get the mpl build to find the xcode libpng and freetype libs I had
> to install pkgconfig, as I described at

> so it is not exactly automatic.  But it does work, in my experience.

The issue here is not that it isn't automatic -- we could fix that -- 
it's that we can't count on X11 libs being there, particularly on 10.4 
systems.

-Chris



-- 
Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R            (206) 526-6959   voice
7600 Sand Point Way NE   (206) 526-6329   fax
Seattle, WA  98115       (206) 526-6317   main reception

Chr...@no...

John Hunter wrote:
>>  Instead of all of us going through the pain of figuring out how to build
>>  and link static libs for MPL, and PIL, and GDAL, and ???, why don't we
>>  just build against the nice Frameworks here:
>>
>>  http://www.kyngchaos.com/wiki/software:frameworks

> I read your post and perhaps I am missing the obvious, but my basic
> question is: apple provides libpng and freetype with xcode which ships
> with their computers (an optional install from their cd) and these
> work fine with MPL, so why should we require an external dependency?

I'd love it if Apple provided this stuff.

Are they static libs? What versions do they ship them with -- I don't 
have OS-X 10.5, and I don't think I have them -- maybe I need to update 
XCode.

freetype comes with X11, which is optional (though installed by default 
on 10.5).

Also, I need libjpeg for PIL, but I guess that's not an OS-X issue.

Here's the goal:

Be able to easily build and distribute binaries of MPL (and other 
packages that require require similar libs). These binaries should:

   (1) Run on any OS-X 10.4+ system (10.3.9 would be nice too) with 
python.org's 2.5 framework build.

   (2) Allow packaging up with py2app, to get packages that will run on 
any 10.4+ system.

As far as I know, the only way to do that now is to statically link 
against universal builds of all the dependencies that Apple does not 
provide on a stock 10.4 system. The problem is that there doesn't seem 
to be any standard source of Universal binaries for any of these libs 
(and the extra build flags required haven't made it into the source of 
the host projects). Also, it seems a bit silly to have a whole bunch of 
different packages all working hard to bundle in the same libs.

I just built PIL against William's Frameworks, and it was oh so easy -- 
this after spending quite a few hours trying (and not finishing) getting 
the required libs built as Universal.

We can only use Apple's libs if:
   They provide static Universal versions
or
   The dynamic libs are there on All 10.4+ OS-X boxes.

Maybe we can use more Apple libs for 10.5 only builds.

William has some good comments on this in this thread on the pythonmac list:
  - http://mail.python.org/pipermail/pythonmac-sig/2008-April/019988.html

-Chris

-- 
Christopher Barker, Ph.D.
Oceanographer

Emergency Response Division
NOAA/NOS/OR&R            (206) 526-6959   voice
7600 Sand Point Way NE   (206) 526-6329   fax
Seattle, WA  98115       (206) 526-6317   main reception

Chr...@no...

On Fri, Apr 25, 2008 at 11:51 AM, Rich Fought <wha...@fs...> wrote:

>  This error has only appeared since we started using Apache 2.2 instead
>  of 2.0.  I can do the import just fine from the command line in a python
>  2.3 shell.  Any ideas?

My guess is that somewhere on your system you have an old matplotlib
installed that had the namespace package declared, and this is fouling
up your import.

JDH

Hi,

I'm getting the following error when trying to create a plot with
matplotlib.  I am using matplotlib-0.91.2 on CentOS 4 with python 2.3.
We are running it with mod_python and Apache in a web service
configuration.

File
"/usr/lib/python2.3/site-packages/matplotlib-0.91.2_r0-py2.3-linux-i686.egg/matplotlib/dates.py", line 88, in ?
    import matplotlib.ticker as ticker

  File "/usr/lib/python2.3/site-packages/matplotlib-0.91.2_r0-py2.3-linux-i686.egg/matplotlib/ticker.py", line 116, in ?
    from matplotlib import verbose, rcParams

ImportError: cannot import name rcParams

This error has only appeared since we started using Apache 2.2 instead
of 2.0.  I can do the import just fine from the command line in a python
2.3 shell.  Any ideas?

Thanks,
Rich

Antonio Gonzalez wrote:
> Eric Firing wrote:
>> John Hunter wrote:
>>> On Wed, Apr 23, 2008 at 6:45 AM, Antonio Gonzalez <ja...@ca...> wrote:
>>>> Hello,
>>>>
>>>>  I've just updated to the latest svn (5063) and now I cannot create a
>>>>  simple plot. If I just try (in ipython -pylab):
>>>>
>>>>  plot(rand(10))
>>>>
>>>>  I get:
>>>>
>>>>  <type 'exceptions.AttributeError'>: 'module' object has no attribute
>>>>  'masked_invalid'
>>> matplotlib svn requires numpy svn.  Try upgrading your numpy and I
>>> think this bug will go away.
>> I put in a temporary workaround, but what we need is a numpy version 
>> check when mpl is imported.  I can put something in based on parsing 
>> numpy.__version__; is there a better or more standard way to do this?
>>
>> Eric
> 
> Thanks for the replies. I'm now using numpy svn and all works well.
> May I suggest, then -- maybe a warning should indeed arise at build 
> time? Currently, mpl svn recognises non-svn numpy as an acceptable 
> 'required dependency' during the building process (as reported at the 
> beginning of the 'python setup.py build' output).

Antonio,

Good idea. John beat me to it by a little less than an hour, so it is 
done now.  I added the python 2.4 requirement.

Eric

> 
> Antonio

On Fri, Apr 25, 2008 at 6:26 AM, Antonio Gonzalez <ja...@ca...> wrote:

>  Thanks for the replies. I'm now using numpy svn and all works well.
>  May I suggest, then -- maybe a warning should indeed arise at build
>  time? Currently, mpl svn recognises non-svn numpy as an acceptable
>  'required dependency' during the building process (as reported at the
>  beginning of the 'python setup.py build' output).

Done in r5074.  I don't have an older numpy lying around to test my
changes, but I think I got it right.  In check_for_numpy:

    major, minor1, minor2 = map(int, numpy.__version__.split('.')[:3])
    if major<1 or (major==1 and minor1<1):
        print_status("numpy version", "no")
        print_message("You must install numpy 1.1 or later to build
matplotlib.")

        return False


JDH

I'm not able to reproduce this bug.  What version of matplotlib are you 
using and which backend?

Cheers,
Mike

Sunzen Wang wrote:
> Hi,
>
> As title, When extremely zooming in by 'Zoom to Rectangle' navigation 
> button, there will  strange plot. A script is attached and two strange 
> plots are attached. The problem can be easily reproduced  by selecting 
> a tiny(Please refer to xaxis on attached strange plots for a sense) 
> rectangle area which contains a vertexes.
> Does anyone notice the problem and has something to say about it? Is 
> there some limitation in zoom operation?  
>
> Thank you for your opinion and guidance.
>
> Regards
> -- 
> sunzen
> <<freedom & enjoyment>>
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------
>
> ------------------------------------------------------------------------
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
> Don't miss this year's exciting event. There's still time to save $100. 
> Use priority code J8TL2D2. 
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> ------------------------------------------------------------------------
>
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

There are at least a couple of fishy things here.  It doesn't seem to 
find the Vera fonts that matplotlib installs in mpl-data.  Did you 
remove them, or perhaps the Ubuntu or Debian packagers removed them?  
Then at least the default font would be correct (and not cmr10.ttf, 
which is a very bad choice since it uses a TeX encoding).

As for why it is not picking up FreeSans like you request, my best guess 
is that the default properties to not align correctly with it.  This is 
a major shortcoming of the font looking mechanism in 0.90 that was 
addressed in 0.91.  There is a possible workaround that is somewhat 
painful.  If you run the following command in a shell, you should see 
all of the details about the given font:

 > fc-match -v FreeSans
Pattern has 27 elts (size 32)
        family: "Bitstream Vera Sans"(s)
        familylang: "en"(s)
        style: "Roman"(s)
        stylelang: "en"(s)
        slant: 0(i)(s)
        weight: 80(i)(s)
        width: 100(i)(s)
        size: 12(f)(s)
        pixelsize: 12.5(f)(s)
        foundry: "bitstream"(s)
        hintstyle: 1(i)(w)
        hinting: FcTrue(w)
        verticallayout: FcFalse(s)
        autohint: FcFalse(s)
        globaladvance: FcTrue(s)
        file: "/home/mdroe/.fonts/Vera.ttf"(s)

    etc...

(I don't have FreeSans, so the above is for the next best match on my 
machine, Vera Sans).

Now, if you specify the font as specifically as possible, you may get it 
to grab your font:

rc('font',**{'family':'sans-serif','sans-serif':['FreeSans'],'weight':80, 'style':'Roman'})


(The above will need to be replaced with values for FreeSans, of course).

Let me know if that helps.

Cheers,
Mike

Paul Smith wrote:
> Michael Droettboom <mdroe@...> writes:
>
>   
>> Paul Smith wrote:
>>     
>>> Hi Michael,
>>>
>>> I put in the rc line you suggested below into fonts_demo.py but didn't see 
>>>       
> it 
>   
>>> print any extra info (but did confirm in ipython that rcParams showed 
>>> verbose.level had changed to "annoying"). It just quietly finished 
>>>       
> otherwise. 
>   
>>> Did I miss something here? 
>>>   
>>>       
>> Does it work if you put this into your matplotlibrc?
>>
>>   verbose.level: debug-annoying
>>
>> (Note it's debug-annoying, not simply annoying)
>>     
>>> I've linked the output of fonts_demo.py to;
>>> https://www.box.net/shared/static/o693hq3soo.png
>>>   
>>>       
>> Hmm.  That font is definitely not Vera Sans.  Something really odd is 
>> going on here.
>> I can appreciate that goal -- and AFAIK it does work for other users on 
>>     
> Ubuntu 7.10 so there is probably just
>   
>> some configuration problem here that we can hopefully get to the bottom of.
>>
>> Do you have any customizations in your matplotlibrc?
>>
>> Cheers,
>> Mike
>>
>>     
>
>
> Mike,
>
> I've not made any other changes to matplotlibrc. In fact I only just now have 
> copied the one in /etc to my $HOME/.matplotlib directory. It still seemed to 
> pick up the /etc version as you'll see below, I guess coz I was sudo'd as 
> root? :) anyway...
> Interesting the font search path seems to only include mpl-data fonts, but it 
> does seem to know about the ones in /usr/share/fonts/truetype/freefont. Then 
> fails to use one, so we're always back to cmr10. The output below was for my 
> test plot but it's pretty much the same (longer) story for fonts_demo.py  I 
> tried copying all the freetype fonts into mpl-data/font and everything came 
> out FreeSansOblique. Still failed to find the correct font, but used something 
> a little closer. What do you make of it?
> I'll be away for a while but I'll check the list if I can.
>
> Cheers,
> Paul
>
> debug-annoying dump from my test plot program
> ----------------------------------------
> loaded rc file /etc/matplotlibrc
> matplotlib version 0.90.1
> verbose.level debug-annoying
> interactive is False
> units is True
> platform is linux2
> loaded modules: 
> ['_bisect', 'distutils', 'random', 'datetime', 'matplotlib.tempfile', 'distutil
> s.sysconfig', 'encodings.encodings', 'pytz.cStringIO', 'struct', 'tempfile', 'p
> ytz.os', 'zipimport', 'string', 'encodings.utf_8', 'matplotlib.__future__', 'py
> tz.tzinfo', 'pytz.datetime', 'distutils.re', 'bisect', 'signal', 'matplotlib.py
> tz', 'pytz.tzfile', 'cStringIO', 'locale', 'encodings', 'dateutil', 'matplotlib
> .warnings', 'pytz.pytz', 'matplotlib.sys', 're', 'math', 'fcntl', 'UserDict', '
> distutils.os', 'matplotlib', 'codecs', 'md5', '_locale', 'matplotlib.os', 'thre
> ad', 'itertools', 'distutils.sys', 'os', '__future__', '_sre', '__builtin__', '
> matplotlib.re', 'operator', 'distutils.string', 'matplotlib.datetime', 'posixpa
> th', 'errno', 'binascii', 'sre_constants', 'matplotlib.md5', 'types', 'pytz.sys
> ', '_codecs', 'pytz', 'copy', '_struct', '_types', 'matplotlib.dateutil', 'hash
> lib', 'posix', 'encodings.aliases', 'exceptions', 'sre_parse', 'pytz.bisect', '
> distutils.distutils', 'copy_reg', 'sre_compile', '_hashlib', '_random', 'pytz.s
> truct', 'site', '__main__', 'shutil', 'strop', 'encodings.codecs', 'gettext', '
> pytz.sets', 'stat', 'warnings', 'encodings.types', 'sys', 'os.path', 'pytz.gett
> ext', 'matplotlib.distutils', 'distutils.errors', 'linecache', 'matplotlib.shut
> il', 'sets']
> numerix numpy 1.0.3
> font search path ['/usr/share/matplotlib/mpl-
> data/fonts/ttf', '/usr/share/matplotlib/mpl-data/fonts/afm']
> trying fontname /usr/share/matplotlib/mpl-data/fonts/ttf/cmr10.ttf
> trying fontname /usr/share/matplotlib/mpl-data/fonts/ttf/cmtt10.ttf
> trying fontname /usr/share/matplotlib/mpl-data/fonts/ttf/cmmi10.ttf
> trying fontname /usr/share/matplotlib/mpl-data/fonts/ttf/cmex10.ttf
> trying fontname /usr/share/matplotlib/mpl-data/fonts/ttf/cmsy10.ttf
> trying fontname /usr/share/fonts/truetype/ttf-dejavu/DejaVuSansMono-Bold.ttf
> trying fontname /usr/share/fonts/truetype/ttf-dejavu/DejaVuSerifCondensed-
> Bold.ttf
> trying fontname /usr/share/fonts/truetype/ttf-dejavu/DejaVuSansMono-Oblique.ttf
> trying fontname /usr/share/fonts/truetype/ttf-dejavu/DejaVuSansCondensed-
> Oblique.ttf
> trying fontname /usr/share/fonts/truetype/ttf-dejavu/DejaVuSansCondensed.ttf
> trying fontname /usr/share/fonts/truetype/ttf-dejavu/DejaVuSerif-Italic.ttf
> trying fontname /usr/share/fonts/truetype/freefont/FreeSerifBoldItalic.ttf
> trying fontname /usr/share/fonts/truetype/freefont/FreeMonoOblique.ttf
> trying fontname /usr/share/fonts/truetype/ttf-dejavu/DejaVuSerif-BoldItalic.ttf
> trying fontname /usr/share/fonts/truetype/ttf-dejavu/DejaVuSans.ttf
> trying fontname /usr/share/fonts/truetype/ttf-dejavu/DejaVuSansMono.ttf
> trying fontname /usr/share/fonts/truetype/freefont/FreeSerif.ttf
> trying fontname /usr/share/fonts/truetype/ttf-dejavu/DejaVuSerif-Bold.ttf
> trying fontname /usr/share/fonts/truetype/freefont/FreeSerifBold.ttf
> trying fontname /usr/share/fonts/truetype/ttf-dejavu/DejaVuSerif.ttf
> trying fontname /usr/share/fonts/truetype/ttf-dejavu/DejaVuSerifCondensed-
> Italic.ttf
> trying fontname /usr/share/fonts/truetype/freefont/FreeSansOblique.ttf
> trying fontname /usr/share/fonts/truetype/ttf-dejavu/DejaVuSerifCondensed.ttf
> trying fontname /usr/share/fonts/truetype/ttf-dejavu/DejaVuSansCondensed-
> Bold.ttf
> trying fontname /usr/share/fonts/truetype/freefont/FreeSansBoldOblique.ttf
> trying fontname /usr/share/fonts/truetype/ttf-dejavu/DejaVuSans-Oblique.ttf
> trying fontname /usr/share/fonts/truetype/ttf-dejavu/DejaVuSerifCondensed-
> BoldItalic.ttf
> trying fontname /usr/share/fonts/truetype/freefont/FreeMonoBoldOblique.ttf
> trying fontname /usr/share/fonts/truetype/freefont/FreeSansBold.ttf
> trying fontname /usr/share/fonts/truetype/freefont/FreeSans.ttf
> trying fontname /usr/share/fonts/truetype/ttf-dejavu/DejaVuSans-BoldOblique.ttf
> trying fontname /usr/share/fonts/truetype/freefont/FreeMono.ttf
> trying fontname /usr/share/fonts/truetype/ttf-dejavu/DejaVuSansMono-
> BoldOblique.ttf
> trying fontname /usr/share/fonts/truetype/freefont/FreeSerifItalic.ttf
> trying fontname /usr/share/fonts/truetype/ttf-dejavu/DejaVuSansCondensed-
> BoldOblique.ttf
> trying fontname /usr/share/fonts/truetype/freefont/FreeMonoBold.ttf
> trying fontname /usr/share/fonts/truetype/ttf-dejavu/DejaVuSans-Bold.ttf
> trying fontname /usr/share/fonts/truetype/ttf-dejavu/DejaVuSans-ExtraLight.ttf
> $HOME=/root
> CONFIGDIR=/root/.matplotlib
> loaded ttfcache file /root/.matplotlib/ttffont.cache
> matplotlib data path /usr/share/matplotlib/mpl-data
> backend Agg version v2.2
> backend_agg.new_figure_manager
> FigureCanvasAgg.draw
> RendererAgg.__init__
> RendererAgg.__init__ width=640.0,                         height=480.0
> RendererAgg.__init__ _RendererAgg done
> RendererAgg.__init__ done
> RendererAgg._get_agg_font
> 	findfont failed Arial
> 	findfont failed FreeSans
> Could not match FreeSans, normal, normal.  Returning /usr/share/matplotlib/mpl-
> data/fonts/ttf/cmr10.ttf
> RendererAgg._get_agg_font
> RendererAgg.draw_text
> RendererAgg._get_agg_font
> ----cut bunch of rendering stuff------
>
>
>
>
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference 
> Don't miss this year's exciting event. There's still time to save $100. 
> Use priority code J8TL2D2. 
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>   

-- 
Michael Droettboom
Science Software Branch
Operations and Engineering Division
Space Telescope Science Institute
Operated by AURA for NASA

Eric Firing wrote:
> John Hunter wrote:
>> On Wed, Apr 23, 2008 at 6:45 AM, Antonio Gonzalez <ja...@ca...> wrote:
>>> Hello,
>>>
>>>  I've just updated to the latest svn (5063) and now I cannot create a
>>>  simple plot. If I just try (in ipython -pylab):
>>>
>>>  plot(rand(10))
>>>
>>>  I get:
>>>
>>>  <type 'exceptions.AttributeError'>: 'module' object has no attribute
>>>  'masked_invalid'
>> matplotlib svn requires numpy svn.  Try upgrading your numpy and I
>> think this bug will go away.
> 
> I put in a temporary workaround, but what we need is a numpy version 
> check when mpl is imported.  I can put something in based on parsing 
> numpy.__version__; is there a better or more standard way to do this?
> 
> Eric

Thanks for the replies. I'm now using numpy svn and all works well.
May I suggest, then -- maybe a warning should indeed arise at build 
time? Currently, mpl svn recognises non-svn numpy as an acceptable 
'required dependency' during the building process (as reported at the 
beginning of the 'python setup.py build' output).

Antonio

Hello,
Thank you for the suggestion. However, I am refering to the
canvas.restore_region, draw_artist, blit, gui_repaint sort of
animation.
Glenn

On Thu, Apr 24, 2008 at 11:13 PM, Matthias Michler
<Mat...@gm...> wrote:
> Hello Glenn
>
>  Do you refer to a special example?
>  Maybe the following helps you.
>  ------------------------------------------------------------------------------
>  from pylab import *
>
>  ion()
>  ax = subplot(111)
>  # ... some plotting
>  ax.relim()                      # reset intern limits of the current axes
>  ax.autoscale_view()   # reset axes limits
>
>  ioff()
>  show()
>  --------------------------------------------------------------------------------------
>
>  Good luck,
>  Matthias
>
>
>
>  On Friday 25 April 2008 08:01:24 G Jones wrote:
>  > I would like to extend the animated plot paradigm to an application
>  > where I need to autoscale the vertical axis each time the plot is
>  > updated. Any suggestions as to how to do so? I assume I need to tell
>  > the axis to autoscale, then draw the axis' artist. However, I am not
>  > sure how to do these things, I'm having trouble finding the
>  > appropriate methods in the matplotlib class documentation.
>  > Thanks,
>  > Glenn
>  >
>  > -------------------------------------------------------------------------
>  > This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
>  > Don't miss this year's exciting event. There's still time to save $100.
>  > Use priority code J8TL2D2.
>  > http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/java
>  >one _______________________________________________
>  > Matplotlib-users mailing list
>  > Mat...@li...
>  > https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>
>
>
>  -------------------------------------------------------------------------
>  This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
>  Don't miss this year's exciting event. There's still time to save $100.
>  Use priority code J8TL2D2.
>  http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone
>  _______________________________________________
>  Matplotlib-users mailing list
>  Mat...@li...
>  https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>

Hello Glenn

Do you refer to a special example?
Maybe the following helps you.
------------------------------------------------------------------------------
from pylab import *

ion()
ax = subplot(111)
# ... some plotting
ax.relim()                      # reset intern limits of the current axes
ax.autoscale_view()   # reset axes limits

ioff()
show()
--------------------------------------------------------------------------------------

Good luck,
Matthias

On Friday 25 April 2008 08:01:24 G Jones wrote:
> I would like to extend the animated plot paradigm to an application
> where I need to autoscale the vertical axis each time the plot is
> updated. Any suggestions as to how to do so? I assume I need to tell
> the axis to autoscale, then draw the axis' artist. However, I am not
> sure how to do these things, I'm having trouble finding the
> appropriate methods in the matplotlib class documentation.
> Thanks,
> Glenn
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by the 2008 JavaOne(SM) Conference
> Don't miss this year's exciting event. There's still time to save $100.
> Use priority code J8TL2D2.
> http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/java
>one _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

I would like to extend the animated plot paradigm to an application
where I need to autoscale the vertical axis each time the plot is
updated. Any suggestions as to how to do so? I assume I need to tell
the axis to autoscale, then draw the axis' artist. However, I am not
sure how to do these things, I'm having trouble finding the
appropriate methods in the matplotlib class documentation.
Thanks,
Glenn

Hi,

As title, When extremely zooming in by 'Zoom to Rectangle' navigation
button, there will  strange plot. A script is attached and two strange plots
are attached. The problem can be easily reproduced  by selecting a
tiny(Please refer to xaxis on attached strange plots for a sense) rectangle
area which contains a vertexes.
Does anyone notice the problem and has something to say about it? Is there
some limitation in zoom operation?

Thank you for your opinion and guidance.

Regards
-- 
sunzen
<<freedom & enjoyment>>

On Thu, Apr 24, 2008 at 2:43 AM, G Jones <gle...@gm...> wrote:
> I'm confused, because I don't see any place where self.canvas.draw is
>  called in the code1 version. Also, when I resize the figure, the
>  background region changes, so the plot gets messed up as I have
>  noticed before with this method. Does anyone know a good way to
>  recapture a clean background, in particular when the image is resized?

It's a good question.  There is no explicit fig.canvas.draw in the
code1 example, but there is an implicit one, since the relevant
function calls ("draw_artist", "restore_region" and "blit") occur in
the wx OnTimer method.  These things are GUI dependent, but stuff that
happens in the idle hander or timer handler of GUI toolkits often
happen after the initial mpl draw.

JDH

On Thu, Apr 24, 2008 at 9:24 PM, Christopher Fonnesbeck
<lis...@ma...> wrote:

> > I read your post and perhaps I am missing the obvious, but my basic
> > question is: apple provides libpng and freetype with xcode which ships
> > with their computers (an optional install from their cd) and these
> > work fine with MPL, so why should we require an external dependency?
>
>  Really?? So I'm an idiot -- I dont deny it.
>
>  At any rate, I think I have things working with a static build of both
> these libraries.


I may have spoken too quickly -- I forgot that on my system in order
to get the mpl build to find the xcode libpng and freetype libs I had
to install pkgconfig, as I described at

http://ipython.scipy.org/moin/Py4Science/InstallationOSX

with the following note:

    matplotlib depends on libpng and freetype, both of which are
provided by the xcode package in
    /usr/X11R6, so I am going to point the mpl build to that
directory. sys.platform is "darwin", so edit
    setupext.py and add '/usr/X11R6' to the "basedir" dictionary for
the 'darwin' key. You need to install
    pkgcong-0.22 from http://pkgconfig.freedesktop.org/releases/ (just
configure, sudo make install it) so that
    matplotlib can use it to find an properly configure png and
freetype. You will need to set the pkgcong path

     > export PKG_CONFIG_PATH=/usr/X11/lib/pkgconfig

so it is not exactly automatic.  But it does work, in my experience.

JDH

On 25/04/2008, at 2:03 PM, John Hunter wrote:

> On Thu, Apr 24, 2008 at 11:51 AM, Christopher Barker
> <Chr...@no...> wrote:
>
>> I posted a note about this yesterday, with no replies, so I'll try  
>> again:
>>
>> Instead of all of us going through the pain of figuring out how to  
>> build
>> and link static libs for MPL, and PIL, and GDAL, and ???, why don't  
>> we
>> just build against the nice Frameworks here:
>>
>> http://www.kyngchaos.com/wiki/software:frameworks
>>
>> yes, it's an extra download and install, but it's easy, they can be
>> provided by package distributors, and they can be shared by a bunch  
>> of
>> python packages (and other *nix-y software). See my message yesterday
>> for more detail.
>
> Hey Chris,
>
> I read your post and perhaps I am missing the obvious, but my basic
> question is: apple provides libpng and freetype with xcode which ships
> with their computers (an optional install from their cd) and these
> work fine with MPL, so why should we require an external dependency?

Really?? So I'm an idiot -- I dont deny it.

At any rate, I think I have things working with a static build of both  
these libraries.

Thanks,
cf

--
Christopher Fonnesbeck
Dunedin, New Zealand
Skype: chrisfonnesbeck

On Thu, Apr 24, 2008 at 11:51 AM, Christopher Barker
<Chr...@no...> wrote:

>  I posted a note about this yesterday, with no replies, so I'll try again:
>
>  Instead of all of us going through the pain of figuring out how to build
>  and link static libs for MPL, and PIL, and GDAL, and ???, why don't we
>  just build against the nice Frameworks here:
>
>  http://www.kyngchaos.com/wiki/software:frameworks
>
>  yes, it's an extra download and install, but it's easy, they can be
>  provided by package distributors, and they can be shared by a bunch of
>  python packages (and other *nix-y software). See my message yesterday
>  for more detail.

Hey Chris,

I read your post and perhaps I am missing the obvious, but my basic
question is: apple provides libpng and freetype with xcode which ships
with their computers (an optional install from their cd) and these
work fine with MPL, so why should we require an external dependency?

JDH

On Thu, Apr 24, 2008 at 4:11 PM, Antonino Miceli <ant...@gm...> wrote:
> Hi,
>
>   I want to inset one axes within a larger one... as in
>   http://matplotlib.sourceforge.net/screenshots/axes_demo.py and
>   http://matplotlib.sourceforge.net/screenshots/axes_demo_small.png
>
>   but I was wondering if there is an option similar to "best" location
>   in the legend function. So, instead of hardwiring, like:
>   a = axes([.65, .6, .2, .2], axisbg='y'), I like it automatically place
>   the inset in a "best" location!

There isn't any such function, but you could look at the legend code
for loc="best" for inspiration if you want t roll your own.

JDH