matplotlib-users Mailing List for matplotlib (Page 5)

Jon,

One thing you can do is to manually specify the levels to contour for in the
contour call, or just specify the number of contours (and contour() will
figure out the levels for you).  The fourth argument to contour() allows you
to give a sequence of values (or an integer) for the isopleths.  So, if you
want just one line (but have it chosen automatically):

contour(x, y, z, 1)

If you want a contour to always be for the value of 4.5, for example, then:

contour(x, y, z, [4.5])

Should do the trick.

I hope that helps,
Ben Root



On Tue, Jun 22, 2010 at 1:46 PM, Jonathan Slavin <js...@cf...>wrote:

> To all:
>
> I'm making a plot with an image and a contour on it.  I use only one
> level in the call to contour, but it results in two distinct contours,
> an inner closed one and an outer open one.  I want to plot only the
> outer piece.  How might I go about that?  I've been looking at the
> properties of the ContourSet object returned by the call to contour but
> can't find anything useful yet.  Is there an attribute of ContourSet
> objects that contains the (x,y) values for the contour?  Is there some
> way to see that a ContourSet object has separate pieces?
>
> Any help would be appreciated.
>
> Thanks,
> Jon
>
>
>
> ------------------------------------------------------------------------------
> ThinkGeek and WIRED's GeekDad team up for the Ultimate
> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
> lucky parental unit.  See the prize list and enter to win:
> http://p.sf.net/sfu/thinkgeek-promo
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>

Hi all,  I am trying to figure out how I can limit the xaxis date ranges.  I
tried set_xlim(), but that didn't work.  The graph consists of dates for the
xaxis and data for the yaxis.  Currently the xaxis is showing the entire
year's worth of months, even though there are no data for some months.  This
plot is really close to what I want, however, I need to limit the xaxis to a
only a few months.

  weeks    = matplotlib.dates.WeekdayLocator()   # every year
  months   = matplotlib.dates.MonthLocator()  # every month
  monthsFmt = matplotlib.dates.DateFormatter('%b')
  fig = pylab.figure()
  ax = fig.add_subplot(111)
  ax.xaxis.set_major_locator(months)
  ax.xaxis.set_major_formatter(monthsFmt)
  ax.xaxis.set_minor_locator(weeks)
  pylab.bar(x,y)

Super. I will need to study your solution tomorrow.

--
Jinsuo


-----Original Message-----
From: Stan West [mailto:sta...@nr...] 
Sent: Tuesday, June 22, 2010 4:41 PM
To: Nie, Jinsuo; mat...@li...
Subject: RE: [Matplotlib-users] Animated Line2D

> From: Nie, Jinsuo [mailto:jn...@bn...] 
> Sent: Tuesday, June 22, 2010 09:33
...
> I modified the path_editor.py example in order to make a line editor,
as
> attached. The path_editor.py worked fine on Qt4Agg.  However, in the
> line editor, the line was not draggable on the same backend.
...


The problem seems to stem from the line not being marked invalid when
its
set_data method is called.  This can be seen by modifying your
motion_notify_callback method as follows; I removed the previous print
statements and inserted a new one:

    def motion_notify_callback(self, event):
        'on mouse movement'
        if not self.showverts: return
        if self._ind is None: return
        if event.inaxes is None: return
        if event.button != 1: return
        x,y = self.line.get_data()
        x[self._ind] = event.xdata
        y[self._ind] = event.ydata
        self.line.set_data(x, y)
        print self.line._invalid
        self.canvas.restore_region(self.background)
        self.ax.draw_artist(self.line)
        self.canvas.blit(self.ax.bbox)

The x returned by get_data is the same object as line._xorig (a private
attribute of the line object), so the changes you make to elements of x
also
apply to _xorig.  Then, set_data compares the incoming x with _xorig,
sees
that they are the same object, and doesn't set the _invalid attribute to
True.
With _invalid still False, the line is not redrawn.

I tested on Windows 7 with matplotlib 0.99.1 (and saw the same behavior
you
did).  The relevant code in matplotlib's lines.py was changed in
revision 8054
(if I'm interpreting correctly), and that's why John saw the animation
using
more recent matplotlib code.  I checked the last released version
(0.99.3) and
found the same code for set_data as in 0.99.1, so updating to 0.99.3
won't
help.

However, I see two alternative easy solutions.  (1) After calling
self.line.set_data, call self.line.recache, which is what would happen
automatically if the _invalid attribute were True.  (2) Call set_data
with
different objects than the ones you received from get_data.  For
example:

        vertices = zip(*self.line.get_data())
        vertices[self._ind] = event.xdata, event.ydata
        self.line.set_data(zip(*vertices))

The set_data method will then set _invalid to True, enabling the line to
be
redrawn.

> From: Nie, Jinsuo [mailto:jn...@bn...] 
> Sent: Tuesday, June 22, 2010 09:33
...
> I modified the path_editor.py example in order to make a line editor, as
> attached. The path_editor.py worked fine on Qt4Agg.  However, in the
> line editor, the line was not draggable on the same backend.
...


The problem seems to stem from the line not being marked invalid when its
set_data method is called.  This can be seen by modifying your
motion_notify_callback method as follows; I removed the previous print
statements and inserted a new one:

    def motion_notify_callback(self, event):
        'on mouse movement'
        if not self.showverts: return
        if self._ind is None: return
        if event.inaxes is None: return
        if event.button != 1: return
        x,y = self.line.get_data()
        x[self._ind] = event.xdata
        y[self._ind] = event.ydata
        self.line.set_data(x, y)
        print self.line._invalid
        self.canvas.restore_region(self.background)
        self.ax.draw_artist(self.line)
        self.canvas.blit(self.ax.bbox)

The x returned by get_data is the same object as line._xorig (a private
attribute of the line object), so the changes you make to elements of x also
apply to _xorig.  Then, set_data compares the incoming x with _xorig, sees
that they are the same object, and doesn't set the _invalid attribute to True.
With _invalid still False, the line is not redrawn.

I tested on Windows 7 with matplotlib 0.99.1 (and saw the same behavior you
did).  The relevant code in matplotlib's lines.py was changed in revision 8054
(if I'm interpreting correctly), and that's why John saw the animation using
more recent matplotlib code.  I checked the last released version (0.99.3) and
found the same code for set_data as in 0.99.1, so updating to 0.99.3 won't
help.

However, I see two alternative easy solutions.  (1) After calling
self.line.set_data, call self.line.recache, which is what would happen
automatically if the _invalid attribute were True.  (2) Call set_data with
different objects than the ones you received from get_data.  For example:

        vertices = zip(*self.line.get_data())
        vertices[self._ind] = event.xdata, event.ydata
        self.line.set_data(zip(*vertices))

The set_data method will then set _invalid to True, enabling the line to be
redrawn.

To all:

I'm making a plot with an image and a contour on it.  I use only one
level in the call to contour, but it results in two distinct contours,
an inner closed one and an outer open one.  I want to plot only the
outer piece.  How might I go about that?  I've been looking at the
properties of the ContourSet object returned by the call to contour but
can't find anything useful yet.  Is there an attribute of ContourSet
objects that contains the (x,y) values for the contour?  Is there some
way to see that a ContourSet object has separate pieces?

Any help would be appreciated.

Thanks,
Jon

On 06/22/2010 11:39 AM, Benjamin Root wrote:
>
>
> On Tue, Jun 22, 2010 at 3:45 AM, Matthias Michler 
> <Mat...@gm... <mailto:Mat...@gm...>> wrote:
>
>     On Tuesday, June 22, 2010 10:03:06 am Eric Firing wrote:
>     > On 06/21/2010 09:28 PM, Matthias Michler wrote:
>     > > On Monday, June 21, 2010 06:30:04 pm Eric Firing wrote:
>     > >> On 06/21/2010 06:10 AM, Matthias Michler wrote:
>     > >>> Hello list,
>     > >>>
>     > >>> I'm encountering a strange problem with the
>     RectangleSelector using the
>     > >>> latest version of svn. Namely it doesn't work if it wasn't
>     initialized
>     > >>> as RS = RectangleSelector(...)
>     > >>> but using
>     > >>> RectangleSelector(...)
>     > >>> in my script.
>     > >>>
>     > >>> I modified the example rectangle_selector.py from the folder
>     > >>> examples/widgets to illustrate my observation.
>     > >>>
>     > >>> Can anybody reproduce my findings or even explain what is
>     going on?
>     > >>
>     > >> If you don't keep a reference to the RectangleSelector object, it
>     > >> vanishes--it is garbage-collected.
>     > >>
>     > >> Eric
>     > >
>     > > Hi Eric,
>     > >
>     > > thanks for your reply. That sounds reasonable, but I'm still
>     confused.
>     > > With the matplotlib release 0.99.1.1 the RectangleSelector
>     works with
>     > > and without a reference to it. Was this old behavior somehow
>     unintended?
>
>     Hi Eric,
>
>     > I don't know.  In both cases, are you trying it in a script, and
>     running
>     > it outside ipython?  Ipython keeps references to inputs and outputs.
>
>     yes I'm just using
>
>     python rectangle_selector.py
>
>     with the slightly modified script I have sent last time for
>     matplotlib-svn and
>     additionally comment out the 'button' - keyword argument for the
>     release
>     0.99.1.1. The only difference between the two runs is whether
>     matplotlib-svn is
>     found in the PYTHONPATH or not.
>
>     > There haven't been many changes to widgets.py, and I don't see
>     anything
>     > that could account for the difference I also don't see what
>     could keep
>     > it alive if you don't keep a reference to it.
>     >
>     > If the same externally-run script works differently in this respect
>     > between the two mpl versions, then I'm baffled.
>
>     I'm baffled, too. That was what made starting this thread and hope
>     for an
>     explanation, what I'm doing wrong.
>
>     Kind regards,
>     Matthias
>
>
> I could have sworn that there was a bug fix a month or two ago dealing 
> with what appeared to be a memory leak of some sort.  It seemed that 
> some stuff was not getting garbage-collected because they weren't 
> completely dereferenced.  I seem to recall that it had something to do 
> with various backend action callbacks not being dis-connected when 
> finished (or the action was being connected too many times).
>
> Maybe that might explain the difference in behavior (that is, that the 
> old behavior was a "bug" not a "feature")?
Yes, precisely.

Mike

-- 
Michael Droettboom
Science Software Branch
Space Telescope Science Institute
Baltimore, Maryland, USA

On Tue, Jun 22, 2010 at 3:45 AM, Matthias Michler
<Mat...@gm...>wrote:

> On Tuesday, June 22, 2010 10:03:06 am Eric Firing wrote:
> > On 06/21/2010 09:28 PM, Matthias Michler wrote:
> > > On Monday, June 21, 2010 06:30:04 pm Eric Firing wrote:
> > >> On 06/21/2010 06:10 AM, Matthias Michler wrote:
> > >>> Hello list,
> > >>>
> > >>> I'm encountering a strange problem with the RectangleSelector using
> the
> > >>> latest version of svn. Namely it doesn't work if it wasn't
> initialized
> > >>> as RS = RectangleSelector(...)
> > >>> but using
> > >>> RectangleSelector(...)
> > >>> in my script.
> > >>>
> > >>> I modified the example rectangle_selector.py from the folder
> > >>> examples/widgets to illustrate my observation.
> > >>>
> > >>> Can anybody reproduce my findings or even explain what is going on?
> > >>
> > >> If you don't keep a reference to the RectangleSelector object, it
> > >> vanishes--it is garbage-collected.
> > >>
> > >> Eric
> > >
> > > Hi Eric,
> > >
> > > thanks for your reply. That sounds reasonable, but I'm still confused.
> > > With the matplotlib release 0.99.1.1 the RectangleSelector works with
> > > and without a reference to it. Was this old behavior somehow
> unintended?
>
> Hi Eric,
>
> > I don't know.  In both cases, are you trying it in a script, and running
> > it outside ipython?  Ipython keeps references to inputs and outputs.
>
> yes I'm just using
>
> python rectangle_selector.py
>
> with the slightly modified script I have sent last time for matplotlib-svn
> and
> additionally comment out the 'button' - keyword argument for the release
> 0.99.1.1. The only difference between the two runs is whether
> matplotlib-svn is
> found in the PYTHONPATH or not.
>
> > There haven't been many changes to widgets.py, and I don't see anything
> > that could account for the difference I also don't see what could keep
> > it alive if you don't keep a reference to it.
> >
> > If the same externally-run script works differently in this respect
> > between the two mpl versions, then I'm baffled.
>
> I'm baffled, too. That was what made starting this thread and hope for an
> explanation, what I'm doing wrong.
>
> Kind regards,
> Matthias
>
>
I could have sworn that there was a bug fix a month or two ago dealing with
what appeared to be a memory leak of some sort.  It seemed that some stuff
was not getting garbage-collected because they weren't completely
dereferenced.  I seem to recall that it had something to do with various
backend action callbacks not being dis-connected when finished (or the
action was being connected too many times).

Maybe that might explain the difference in behavior (that is, that the old
behavior was a "bug" not a "feature")?

Ben Root

I am reposting my problem since I have not been able to solve it myself.
I guess my original question has been buried deeply in this list.

I modified the path_editor.py example in order to make a line editor, as
attached. The path_editor.py worked fine on Qt4Agg.  However, in the
line editor, the line was not draggable on the same backend. The
printout showed that the line (nodal coordinates) had been updated but
it was not redrawn in the axes. I also tested the line editor on WXAgg
and TkAgg and it did not work either. I am using Windows 7.

John Hunter tested this line editor on his system and found it was
working properly.  I wonder whether this is a issue of backend/os.  I
would like invite people to simply run this script and report your
successfulness and your backend/os. It will be especially useful for me
if you are using Qt4Agg on Windows 7. 

Thank you very much.

--
Jinsuo

Many apologises for the slow response ...

I'm quite convinced the path is not an issue.

2010/6/19 Hana Sevcikova <ha...@cs...>:
> I see there are some compatibility issues. What would be the best way to
> deal with it?

This should be the issue.  I think usually the matplotlib binaries are
linked against the same libraries as the Python binaries to avoid such
trouble, but for the 10.6 issue this went wrong somehow?  I don't
know.

A possibility would be to compile Python and matplotlib yourself.
This can, for matplotlib, be somewhat troublesome.  There is a
recommended way via the make.osx script, and "my" way via tweaking of
the config files.  The recommended way downloads freetype2 etc. into a
local directory and does afaik hard linking, "my" way links it the
usual dynamic way against system-wide installed libraries.  The
make.osx way is way from perfect, but it should work, albeit I
personally like the other way much more, since it appears much more
clean to me.  Tell me what you prefer.  If you prefer "my" way, I will
give you detailed instructions, with the make.osx way I'm neither
comfortable nor acquainted, maybe John can help you then.  There's
also a recent thread about building matplotlib on Mac (10.6 if I'm not
mistaken) with make.osx.

Friedrich

On 06/21/2010 09:28 PM, Matthias Michler wrote:
> On Monday, June 21, 2010 06:30:04 pm Eric Firing wrote:
>> On 06/21/2010 06:10 AM, Matthias Michler wrote:
>>> Hello list,
>>>
>>> I'm encountering a strange problem with the RectangleSelector using the
>>> latest version of svn. Namely it doesn't work if it wasn't initialized
>>> as RS = RectangleSelector(...)
>>> but using
>>> RectangleSelector(...)
>>> in my script.
>>>
>>> I modified the example rectangle_selector.py from the folder
>>> examples/widgets to illustrate my observation.
>>>
>>> Can anybody reproduce my findings or even explain what is going on?
>>
>> If you don't keep a reference to the RectangleSelector object, it
>> vanishes--it is garbage-collected.
>>
>> Eric
>
> Hi Eric,
>
> thanks for your reply. That sounds reasonable, but I'm still confused. With
> the matplotlib release 0.99.1.1 the RectangleSelector works with and without a
> reference to it. Was this old behavior somehow unintended?

I don't know.  In both cases, are you trying it in a script, and running 
it outside ipython?  Ipython keeps references to inputs and outputs.

There haven't been many changes to widgets.py, and I don't see anything 
that could account for the difference.  I also don't see what could keep 
it alive if you don't keep a reference to it.

If the same externally-run script works differently in this respect 
between the two mpl versions, then I'm baffled.

Eric

>
> Kind regards,
> Matthias
>
> ------------------------------------------------------------------------------
> ThinkGeek and WIRED's GeekDad team up for the Ultimate
> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
> lucky parental unit.  See the prize list and enter to win:
> http://p.sf.net/sfu/thinkgeek-promo
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

You should be able to use
http://leejjoon.github.com/mpl_toolkits-gridspec/
for unequal-size plots of the type you describe.

Alan Isaac

On Mon, Jun 21, 2010 at 2:33 PM, Jeffrey Blackburne <je...@mi...> wrote:
> I have used add_axes() to do this in the past. E.g.,
>
> import matplotlib.pyplot as plt
>
> fig = plt.figure()
> leftmarg = 0.125   # change these numbers to taste
> botmmarg = 0.125
> width = 0.825
> height = 0.825
> frac = 2./3.
> ax0 = fig.add_axes([leftmarg, botmmarg, width, frac*height])
> ax1 = fig.add_axes([leftmarg, botmmarg+frac*height, width, (1-frac)*height])
> ax1.xaxis.set_ticklabels([])
> plt.show()
>
> Sorry it is in object-oriented style instead of pylab style...
>

Thanks!  This looks like it might work.  I'll give it a try.
Jeremy

I have used add_axes() to do this in the past. E.g.,

import matplotlib.pyplot as plt

fig = plt.figure()
leftmarg = 0.125   # change these numbers to taste
botmmarg = 0.125
width = 0.825
height = 0.825
frac = 2./3.
ax0 = fig.add_axes([leftmarg, botmmarg, width, frac*height])
ax1 = fig.add_axes([leftmarg, botmmarg+frac*height, width, (1-frac) 
*height])
ax1.xaxis.set_ticklabels([])
plt.show()

Sorry it is in object-oriented style instead of pylab style...


On Jun 21, 2010, at 3:13 PM, Jeremy Conlin wrote:

> I have followed this excellent example:
> http://matplotlib.sourceforge.net/examples/pylab_examples/ 
> ganged_plots.html
>
> but I would like my plots to be 2/3 and 1/3 of the total height of the
> figure (I only have 2 plots).  What do I have to do to specify the
> relative sizes of the figures?
>
> Thanks,
> Jeremy
>
> ---------------------------------------------------------------------- 
> --------
> ThinkGeek and WIRED's GeekDad team up for the Ultimate
> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
> lucky parental unit.  See the prize list and enter to win:
> http://p.sf.net/sfu/thinkgeek-promo
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

Jeremy Conlin <jlc...@gm...>
> I have followed this excellent example:
> http://matplotlib.sourceforge.net/examples/pylab_examples/ganged_plots.html
> 
> but I would like my plots to be 2/3 and 1/3 of the total height of the
> figure (I only have 2 plots).  What do I have to do to specify the
> relative sizes of the figures?

may something like

ax1 = fig.add_subplot(311)
ax2 = fig.add_subplot(212)

work?

if I look at pyplot.setp(ax1) I see a lot of things (like "position" or 
"anchor" or "axes_locator") which might work.

Good luck,

Malte

I have followed this excellent example:
http://matplotlib.sourceforge.net/examples/pylab_examples/ganged_plots.html

but I would like my plots to be 2/3 and 1/3 of the total height of the
figure (I only have 2 plots).  What do I have to do to specify the
relative sizes of the figures?

Thanks,
Jeremy

This doesn't solve the original problem and I know I worked out a way to do
it before my hard disk messed up! But it seems you can get a version going
through macports...

sudo port install py26-matplotlib
sudo port install python_select
sudo python_select python26

then edit your .matplotlib/matplotlibrc file (make one if you don't have
it). And put backend: macosx into it.

Should work fine. Does for me. Now I don't know how one would set python up
so it doesn't find my other version, other than moving paths around. Or
setting it up so easy_install using the /opt/ version of python. Anyone?

thanks

Martin
-- 
View this message in context: http://old.nabble.com/building-on-MAC-snow-leopard-tp28947568p28951913.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

On 06/21/2010 06:10 AM, Matthias Michler wrote:
> Hello list,
>
> I'm encountering a strange problem with the RectangleSelector using the latest
> version of svn. Namely it doesn't work if it wasn't initialized as
> RS = RectangleSelector(...)
> but using
> RectangleSelector(...)
> in my script.
>
> I modified the example rectangle_selector.py from the folder examples/widgets
> to illustrate my observation.
>
> Can anybody reproduce my findings or even explain what is going on?

If you don't keep a reference to the RectangleSelector object, it 
vanishes--it is garbage-collected.

Eric

>
> Thanks in advance for any comments.
>
> Kind regards,
> Matthias

> Which 2.6?

Any would be better than none, but I have 2.6.5 (the most recent) from 
python.org.

>  think that needs the 2.6 from Python.org -- I'd try that if it's not
> what you're using already -- if you are, then what errors, etc do you get?

That's not the problem, as that's the version of Python I have.  The 
problem is that the installer doesn't recognize that Python is installed 
and hence won't let matplotlib be installed at all.
-- 

R. Padraic Springuel
Research Assistant
Department of Physics and Astronomy
University of Maine
Bennett 309
Office Hours: By Appointment Only

> Do you have some notes on how you achieved this?  It is more than I've
> been able to do.

Yes I firstly setup a brand new python, i.e. not the one that ships with
snow leopard (ver2.6.5). Then followed everything on
http://blog.hyperjeff.net/?p=160



>I'm not a build or gcc expert, but am interested in the solution to this
>-- I have also tried (without success) to get this compiled on OS X
>10.6.  A few potentially useful pointers:

>1. Check that you have the latest version of XCode.

yep

> 2. Check that you have a recent version of gfortran.

yep

>3. Check your path to various tools:
> http://mail.scipy.org/pipermail/numpy-discussion/2007-January/025669.html

yep.


I came across this which seems to be the ticket, though this also doesn't
work...

http://www.trondkristiansen.com/?page_id=79

when I follow it through it builds but I get a seg fault when I run it. I
payed more attention to the build and I think the issue stems from the arch
flags...

eg.

[HAL-9000@matplotlib-0.99.3]$ make -f make.osx mpl_build
blah, blah
ld: warning: in /usr/local/lib/libstdc++.dylib, file was built for
unsupported file format which is not the architecture being linked (i386)

thanks

-- 
View this message in context: http://old.nabble.com/building-on-MAC-snow-leopard-tp28947568p28948915.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

On 6/21/10 7:41 AM, mdekauwe wrote:
> So I have successfully built a 64bit version of Numpy, Scipy from svn and am
> using python version 2.6.5. However in trying to follow the instructions o

Do you have some notes on how you achieved this?  It is more than I've
been able to do.

> I had a look at the config.log file in the libpng directory and the main
> thing I can see is...
>
> configure:3266: checking for C compiler default output file name
> configure:3288: gcc -arch i386 -arch x86_64 -I/usr/local/include
> -I/usr/local/include/freetype2 -isysroot /Developer/SDKs/MacOSX10.6.sdk 
> -arch i386 -arch x86_64 -L/usr/local/lib
> -syslibroot,/Developer/SDKs/MacOSX10.6.sdk conftest.c  >&5
> gcc: unrecognized option '-syslibroot,/Developer/SDKs/MacOSX10.6.sdk'
> cc1: error: unrecognized command line option "-arch"
> cc1: error: unrecognized command line option "-arch"
> cc1: error: unrecognized command line option "-arch"
> cc1: error: unrecognized command line option "-arch"
>   

I'm not a build or gcc expert, but am interested in the solution to this
-- I have also tried (without success) to get this compiled on OS X
10.6.  A few potentially useful pointers:

1. Check that you have the latest version of XCode.

2. Check that you have a recent version of gfortran.

3. Check your path to various tools:

http://mail.scipy.org/pipermail/numpy-discussion/2007-January/025669.html

Ian

-- 
Ian Stokes-Rees, PhD                       W: http://hkl.hms.harvard.edu
ijs...@hk...               T: +1 617 432-5608 x75
NEBioGrid, Harvard Medical School          C: +1 617 331-5993

Hi,

So I have successfully built a 64bit version of Numpy, Scipy from svn and am
using python version 2.6.5. However in trying to follow the instructions on
this blog (http://blog.hyperjeff.net/?p=160), namely...

changing the make.osx file to

MACOSX_DEPLOYMENT_TARGET=10.6

PREFIX=/usr/local

## You shouldn't need to configure past this point (and yet…)

PKG_CONFIG_PATH="${PREFIX}/lib/pkgconfig"
CFLAGS="-arch i386 -arch x86_64 -I${PREFIX}/include
-I${PREFIX}/include/freetype2 -isysroot /Developer/SDKs/MacOSX10.6.sdk"
LDFLAGS="-arch i386 -arch x86_64 -L${PREFIX}/lib
-syslibroot,/Developer/SDKs/MacOSX10.6.sdk"
FFLAGS="-arch i386 -arch x86_64"

and uncommenting wxagg = False from the setup.cfg 

I still seem to run into trouble. 

Command I am running is sudo make -f make.osx fetch deps mpl_build
mpl_install

which runs into trouble to do with the libpng lib...

x libpng-1.2.39/scripts/makefile.ne12bsd
checking for a BSD-compatible install... /usr/bin/install -c
checking whether build environment is sane... yes
checking for a thread-safe mkdir -p... ./install-sh -c -d
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for gcc... gcc
checking for C compiler default output file name... 
configure: error: in
`/Users/mdekauwe/src/packages/matplotlib_svn/libpng-1.2.39':
configure: error: C compiler cannot create executables
See `config.log' for more details.
make: *** [png] Error 77

I had a look at the config.log file in the libpng directory and the main
thing I can see is...

configure:3266: checking for C compiler default output file name
configure:3288: gcc -arch i386 -arch x86_64 -I/usr/local/include
-I/usr/local/include/freetype2 -isysroot /Developer/SDKs/MacOSX10.6.sdk 
-arch i386 -arch x86_64 -L/usr/local/lib
-syslibroot,/Developer/SDKs/MacOSX10.6.sdk conftest.c  >&5
gcc: unrecognized option '-syslibroot,/Developer/SDKs/MacOSX10.6.sdk'
cc1: error: unrecognized command line option "-arch"
cc1: error: unrecognized command line option "-arch"
cc1: error: unrecognized command line option "-arch"
cc1: error: unrecognized command line option "-arch"

Not sure what the issue with the arch flag is?

Would really appreciate some thoughts on this, many thanks

Martin
-- 
View this message in context: http://old.nabble.com/building-on-MAC-snow-leopard-tp28947568p28947568.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

Hi Matthias,
Thanks for the script! Now I would like to try to understand why it
works :) . In both of the scripts you sent me, plt.draw() is called
inside the loop to display each image file, and plt.show() is called
outside the loop at the end of the script. I guess what I find
confusing is, how is it that the images are displayed on screen,
inside the loop, *before* plt.show() is called? I would have expected
only the very last image inside the loop to be displayed, using this
program structure. So apparently there is something here I do not
understand...

-Daniel

On Tue, Jun 15, 2010 at 3:26 AM, Matthias Michler
<Mat...@gm...> wrote:
> On Monday, June 14, 2010 10:32:48 pm Daniel Jones wrote:
>> Hi matplotlib users,
>>
>> I'm trying to write a script to loop through a bunch of tiff files,
>> display each image, and choose to accept or reject each image.
>> Something like:
>>
>> for f in files:
>>    im = imread(f)
>>    imshow(im)
>>    # Accept keyboard input to accept or reject image
>>    # Close the image
>>
>>
>> The problem is that I can't figure out how to show multiple images in
>> series. I can't use matplotlib.pyplot.show() because that can only be
>> used once at the very end of a script, and I don't want to show all
>> the images at once. matplotlib.pyplot.draw() seemed like a promising
>> candidate, but it only seems to work if I've already used show() once
>> in the script. It seems like there should be a simple way to do this,
>> but I can't quite seem to find it.
>>
>> Thanks,
>> Daniel
>
> Hi Daniel,
>
> in the attached script I propose two solutions for your problem (just
> uncomment first region and comment second to test the first proposal). The first
> uses plt.waitforbuttonpress and the second key-press-events.
>
> Kind regards,
> Matthias
>
> ------------------------------------------------------------------------------
> ThinkGeek and WIRED's GeekDad team up for the Ultimate
> GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the
> lucky parental unit.  See the prize list and enter to win:
> http://p.sf.net/sfu/thinkgeek-promo
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>
>

R. Padraic Springuel wrote:
> Has anyone created installation package for matplotlib 0.99.3 that is 
> compatible with MAC OS 10.5 and Python 2.6? 

Which 2.6?

> One one on the download 
> site for MAC OS 10.6 doesn't work on my system (presumably because I'm 
> still working with Leopard because everything else is up to date).

I think that needs the 2.6 from Python.org -- I'd try that if it's not 
what you're using already -- if you are, then what errors, etc do you get?

-CHB


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

Dear Malte Dik,

Yes, yes we can draw many figures in single figurecanvas. I have
understood how to implement my requirement.

I shall go through once again some topics in matplotlib and pyqt.

Thank you,
Sathishkumar.



On 6/19/10, Malte Dik <mal...@we...> wrote:
> Hi,
>
> you could savefig the plots as pdf and then print that. If you want multiple
> figures on one page you might ask yourself, if those figures have to be
> figure-
> objects in the matplotlib-sense or if they simply can be represented by
> different axes, which you could put into one figure (in the
> matplotlib-sense)
> and savefig that.
>
> So what I recommend is reading about the figure and axes objects and what
> they
> mean in matplotlib.
>
>
> Sincerely,
>
> Malte
>
>> Dear all,
>>
>> I have been developing an application with Pyqt and Matplotlib. I have
>> print mutilple figures either separately or using in a single page. Please
>> can you give a some ideas how to implement this.
>>
>> With Thanks
>> Sathishkumar
>

Dear all,

I have been developing an application with Pyqt and Matplotlib. I have print
mutilple figures either separately or using in a single page. Please can you
give a some ideas how to implement this.

With Thanks
Sathishkumar