matplotlib-users Mailing List for matplotlib (Page 5)

Hi, All

I am trying to add ylable to:

ax1 = plt.subplot2grid((1,3), (0,0), colspan=2)

But got the following error: no 'set_ylable';

Here is my code:

import matplotlib.pyplot as plt
import numpy as np

ax1 = plt.subplot2grid((1,3), (0,0), colspan=2)
ax2 = plt.subplot2grid((1,3), (0,2), colspan=1)

N = 2
Spot = (6.29, 3.47)
Avg = (20.11,18.47)
Ody = (6.39,3.98)
Medium = (6.7,6.12)

ind = np.arange(N)+0.10  # the x locations for the groups
width = 0.15      # the width of the bars

ax1.bar(ind, Spot, width, color='0.35',hatch="\\")
ax1.bar(ind+width, Avg, width, color='0.55',hatch="//")
ax1.bar(ind+2*width, Ody, width, color='0.75',hatch="+")
ax1.bar(ind+3*width, Medium, width, color='0.15',hatch=".")
ax1.set_xticks(ind+2*width)
ax1.set_xticklabels(('Static', 'Dynamic'))
#ax1.set_ylable("Incorrect Decision Ratio (%)")


Regards!
Yu

Can a tick label be on two separate lines? For example:

LabelsList = ['Howard', 'Vince', 'Bob', 'Naboo the Enigma']

xlabels = ax.set_xticklabels( LabelsList, rotation=35,
horizontalalignment='right', fontstyle='italic', fontsize='10')

How can I put "Naboo the Enigma" on two lines? I've tried to enter newlines
and carriage returns in the list element (e.g. 'Naboo\n the Enigma') without
any luck.
-- 
View this message in context: http://old.nabble.com/newline-characters-in-tick-labels-tp32852034p32852034.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

Is there a way to format tick labels separately? For example:

LabelsList = ['Prospero', 'Miranda', 'Caliban', 'Ariel']

xlabels = ax.set_xticklabels( LabelsList, rotation=35,
horizontalalignment='right', fontstyle='italic', fontsize='10')

will give me italicized x tick labels; however, what if I want to italicize
all, but Prospero? Is there a way to format each label separately?
-- 
View this message in context: http://old.nabble.com/Separate-formatting-for-tick-labels-tp32852024p32852024.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

On Tue, Nov 15, 2011 at 2:45 PM, Y.Wu <yw...@gm...> wrote:
> Hi, all
> I have installed v1.1.0 from source code at :
> /usr/local/lib/python2.6/dist-packages/matplotlib
> But whenever I am using python test.py, it still refers to the old v0.99.
> could you please tell me how to update to the new version ?

Here are some instructions to uninstall a previous version:

http://matplotlib.sourceforge.net/faq/installing_faq.html#how-to-completely-remove-matplotlib

Alejandro.

Here you go.

Have attached the log file from the build (Windows 7 (64 bit)) using VS2008.

Best regards,

Mads

On Tue, Nov 15, 2011 at 2:45 PM, Michael Droettboom <md...@st...> wrote:
> I'd love to see the compiler logs and try to fix what I can.  I don't have a
> Windows install to test, but maybe I can resolve the more obvious ones.
>
> Mike
>
> On 11/08/2011 05:49 AM, Mads Ipsen wrote:
>
> Hi,
>
> Thanks to the help from Christoph, I have been able to build
> matplotlib-1.1.0 on both Win XP-32 and 64.
>
> I have noticed though, that quite a few warnings are produced when the
> source is compiled. Is this something that the core developers would like to
> fix, or is it a 'don't care' thing? If the info is useful, I'd be happy to
> post it somewhere.
>
> Best regards,
>
> Mads
>
> --
> +-----------------------------------------------------+
> | Mads Ipsen                                          |
> +----------------------+------------------------------+
> | Gåsebæksvej 7, 4. tv |                              |
> | DK-2500 Valby        | phone:          +45-29716388 |
> | Denmark              | email:  mad...@gm... |
> +----------------------+------------------------------+
>
>
> ------------------------------------------------------------------------------
> RSA(R) Conference 2012
> Save $700 by Nov 18
> Register now
> http://p.sf.net/sfu/rsa-sfdev2dev1
>
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>
>
> --
> Michael Droettboom
> Science Software Branch
> Space Telescope Science Institute
> Baltimore, Maryland, USA
>
> ------------------------------------------------------------------------------
> RSA(R) Conference 2012
> Save $700 by Nov 18
> Register now
> http://p.sf.net/sfu/rsa-sfdev2dev1
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>
>

Hi, all

I have installed v1.1.0 from source code at :

/usr/local/lib/python2.6/dist-packages/matplotlib

But whenever I am using python test.py, it still refers to the old v0.99.

could you please tell me how to update to the new version ?

thanks a lot.

Regards!
Yu

On 15 November 2011 00:18, Daniel Welling <dan...@gm...> wrote:

> Greetings.
>
> I recently found myself in the position of needing to plot polar,
> irregularly spaced data.  I've done similar using regularly spaced values
> with no problem.  However, I've found that when the points become greatly
> scattered, the triangulation does not translate from rectangular to polar
> very well.  Below, find a code example that shows this; though it is much
> "better" than my real-world case that uses simulation results.
>  Essentially, in the translation from regular to polar axes, many of the
> triangles overlap others, many features of the plot are lost, and the plot
> looks mangled in certain regions, esp. across the theta=0 boundary.  While
> subtle here (but MUCH worse in the results I'm trying to visualize), some
> of the triangles lie outside of the triangulated region.  It isn't merely
> that the polar plot is suffering from poor data coverage; the triangulation
> is not working properly in polar coordinates and the results are
> quantitatively different than the rectangular plot.
>
> The obvious work-around for this problem illustrates the issue more
> clearly.  If we convert rad, theta back to x, y and do a rectangular plot,
> the triangulation is much better (not only is there no issue around
> theta=0, but there are no overlapping triangles), all of the details of the
> non-polar version are maintained, and the plot looks great.  This is not
> the best solution, as polar plots in Matplotlib are quite elegant.
>
> Any help here would be appreciated.  It could be that triangulations are
> just not suited for polar plots; it could be that the theta=0 issue throws
> things off, etc; I'm just not sure.  It would be perfect if I could use the
> polar axes in the end.
>
> Thanks.
> -dw
>

Daniel,

I can't give you much help but I can provide some explanation.  If you
don't specify a triangulation of your own, the matplotlib tri* functions
use lib/matplotlib/delaunay/triangulate as a black box.  You are right in
saying that it is not suited to polar plots; it assumes cartesian axes.
 The lib/matplotlib/tri/* functions use triangulations that comprise a
number of triangles with vertices ordered in an anticlockwise manner.  The
delaunay triangulation returns such triangles on a cartesian grid.  But if
you transform a cartesian triangulation to a polar grid, you invariably end
up with some triangles which are ordered clockwise and hence also overlap
each other.  Tricontour doesn't like this and gives the best results it can
given that is has been passed an incorrect triangulation, which from your
point of view means the wrong results.

In addition, as you have noticed there are other problems around theta=0.
 In a polar plot points near theta=0 are visible both from the low and high
theta ends of the plot, whereas in a cartesian plot they are only visible
from one side unless you take steps to repeat such points so the wraparound
works.

The answer, unfortunately, is to specify your own triangulation using the
'triangles' keyword in your calls to the tri* functions.  I suspect that
most people who regularly use the tri* functions obtain their
triangulations from elsewhere rather than using the matplotlib delaunay
code.

It should be possible to pass your polar coordinates to delaunay to obtain
the triangulation in polar space, then use this triangulation in your tri*
polar plots.  However, I've tried it (albeit briefly) and it appears to
hang the delaunay code.

An alternative may be to take a look at griddata (there is an example in
matplotlib's pylab_examples directory).  It is difficult for me to
recommend such an approach, however, as I wrote the tri* functions so that
I wouldn't have to use griddata!

Ian

Hi Micheal,

I didn't see your response, apologies for the frustrated post.  I am building a completely fresh VE and when the testing fails I blow it away and start from scratch.  I will try your suggestion on my next iteration and see if that fixes the problem.

Ideally, I'd like to "pip install" the module into my VE, but the same problem persists with that approach.  My pip command is: 

pip install -f http://downloads.sourceforge.net/project/matplotlib/matplotlib/matplotlib-1.0/matplotlib-1.0.0.tar.gz matplotlib 

per the suggestion from http://seanbehan.com/mac-os-x/installing-matplotlib-on-os-x-for-python-version-2-6-1/

If my setup.cfg file isn't configured correctly, could it cause an issue like this?  I would think that the test sub-directories would be required, no matter the setup.  I've attached the installation output below in case that sheds any light on the problem.

On 11/15/2011 06:23 AM, Volker Blum wrote:
> Hi Ben,
>
> thanks for the answer, ... umm, but did the person making the change
> realize that such error messages are exposed to users who do not have
> any idea what python is.
>
> I would plead(*) with anyone that functionality that is not harmful
> please not be deprecated like this. Scripts based on matplotlib, as
> software, will have a much longer life than that 1 year it took to
> deprecate this harmless function.
>
> best wishes Volker
>
> (*) I know it's free software, and I have neither right nor desire to
> demand anything like this. Hence the "plead".
>
> ... problem is, all we can do is evaluate whether matplotlib is safe
> to base our own work on here for the long term. The simple fallout
> from such a  deprecation can be fixed in our own internal repository,
> sure ... but this quite central script will remain broken from the
> point of view of our users for a long time.

Volker,

The simple answer to your question about safety is "no, if safety in the 
long term requires that the code you write now must work with any future 
version of mpl".  This is true throughout the software ecosystem of 
interdependent libraries--even in non-free software.  It is particularly 
applicable to organically evolving libraries like mpl.  We want the 
evolution of mpl to be as comfortable for users as possible, balanced 
with the need to improve.  This includes the need to remove 
functionality that is marginal, obsolete, or inappropriate.  All code 
has a maintenance cost.  In addition, marginal or redundant 
functionality has a cost to users: increased learning time and likely 
confusion for anyone working with the library.

Eric

>
> On Nov 15, 2011, at 4:50 PM, Benjamin Root wrote:
>
>> Others are probably more suited for explaining the hows and whys of
>> mlab.py, but I will give it a crack.  mlab.py was originally made
>> to help assist users transitioning from Matlab over to matplotlib.
>> Some functions that were probably considered to be top-tier in
>> Matlab had to be accessed in sub-modules in NumPy, or were only
>> available in the scipy packages. mlab.py attempted to address
>> that.
>>
>> There is also the issue where we were attempting to bridge
>> compatibility with the old Numerix package which did not have many
>> of these things at all.  Support for Numerix has long been
>> deprecated and so the need for many of the functions in mlab.py has
>> gone away.  This is why we now refer to the equivalent numpy
>> function in the deprecation messages.
>>
>> In v1.1.0, the norm() function is completely removed and you will
>> not even get a deprecation message at all.  The easiest solution is
>> to adapt your scripts to use the numpy equivalents as suggested in
>> the messages.
>>
>> Cheers! Ben Root
>
>
>
>
>
>
> ------------------------------------------------------------------------------
>
>
RSA(R) Conference 2012
> Save $700 by Nov 18 Register now http://p.sf.net/sfu/rsa-sfdev2dev1
> _______________________________________________ Matplotlib-users
> mailing list Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

Dear All,

I have a problem with installation of python(x,y). When I try, it says
"python 2.6.2 msi was not found" If anyone knows how to resolve this issue,
please help me. My OS is windows 7 64bit.

 If this mailing lists does not help pyhton(x,y) issue, please lead me to a
right place.

Thank you very much,

Jun

The matplotlib download says its for python 2.7, but it requires numpy and 
I can only find numpy for version 2.6 of python.  I tried to install numpy 
for 2.6 and it wouldn't work.


Greg Schwarzentraub

Hi Ben,

thanks for the answer, ... umm, but did the person making the change realize that such error messages are exposed to users who do not have any idea what python is.

I would plead(*) with anyone that functionality that is not harmful please not be deprecated like this. Scripts based on matplotlib, as software, will have a much longer life than that 1 year it took to deprecate this harmless function. 

best wishes
Volker

(*) I know it's free software, and I have neither right nor desire to demand anything like this. Hence the "plead".

... problem is, all we can do is evaluate whether matplotlib is safe to base our own work on here for the long term. The simple fallout from such a  deprecation can be fixed in our own internal repository, sure ... but this quite central script will remain broken from the point of view of our users for a long time. 

On Nov 15, 2011, at 4:50 PM, Benjamin Root wrote:

> Others are probably more suited for explaining the hows and whys of mlab.py, but I will give it a crack.  mlab.py was originally made to help assist users transitioning from Matlab over to matplotlib.  Some functions that were probably considered to be top-tier in Matlab had to be accessed in sub-modules in NumPy, or were only available in the scipy packages. mlab.py attempted to address that.
> 
> There is also the issue where we were attempting to bridge compatibility with the old Numerix package which did not have many of these things at all.  Support for Numerix has long been deprecated and so the need for many of the functions in mlab.py has gone away.  This is why we now refer to the equivalent numpy function in the deprecation messages.
> 
> In v1.1.0, the norm() function is completely removed and you will not even get a deprecation message at all.  The easiest solution is to adapt your scripts to use the numpy equivalents as suggested in the messages.
> 
> Cheers!
> Ben Root

On Tue, Nov 15, 2011 at 2:53 AM, Volker Blum <bl...@fh...> wrote:

>
> On Nov 14, 2011, at 5:34 PM, Volker Blum wrote:
>
> > Thanks for the (two!) fast answers on the list. So there is hope :) I'll
> take a look at the fink internals, I guess.
> > best wishes
> > Volker
>
> having said that ... after trying the one piece of software that I need on
> another platform, here's what I get:
>
>  File "[...]", line 84, in <module>
>    length = norm(dot(rlatvec,end) - dot(rlatvec,start))
>  File "/usr/lib64/python2.6/site-packages/matplotlib/mlab.py", line 1998,
> in norm
>    raise NotImplementedError('Deprecated - see numpy.linalg.norm')
> NotImplementedError: Deprecated - see numpy.linalg.norm
>
> The script that I was trying to get to work worked fine on Ubuntu this
> summer. Where has "norm" gone? How can it have been deprecated? It looks
> like a matplotlib problem, hence I am asking here.
>
> [I am also asking out of some curiosity - I am sure the problem can be
> fixed relatively easily, but what I am wondering is, am I looking at a
> problem that came with a new version of matplotlib, am I using too old a
> version of matplotlib?]
>
> best wishes
> Volker
>
>
Others are probably more suited for explaining the hows and whys of
mlab.py, but I will give it a crack.  mlab.py was originally made to help
assist users transitioning from Matlab over to matplotlib.  Some functions
that were probably considered to be top-tier in Matlab had to be accessed
in sub-modules in NumPy, or were only available in the scipy packages.
mlab.py attempted to address that.

There is also the issue where we were attempting to bridge compatibility
with the old Numerix package which did not have many of these things at
all.  Support for Numerix has long been deprecated and so the need for many
of the functions in mlab.py has gone away.  This is why we now refer to the
equivalent numpy function in the deprecation messages.

In v1.1.0, the norm() function is completely removed and you will not even
get a deprecation message at all.  The easiest solution is to adapt your
scripts to use the numpy equivalents as suggested in the messages.

Cheers!
Ben Root

On Mon, Nov 14, 2011 at 7:11 AM, Michael Droettboom <md...@st...> wrote:
> This looks like a bug for the IPython folks.  If you make a file
> containing only "import gtk" and "%run" that file, one gets the same error.

It is a bug of IPython 0.11. The problem is solved in 0.12.

See http://mail.scipy.org/pipermail/ipython-user/2011-November/008734.html
for the details.

Alejandro.

Hey everyone, 

I'm doing a dissertation where I need to vary the size of the points in a 2D
plot. Now I know that you can change the size of every point by changing the
value of markersize to any integer value you want, but how do you put in an
array so that every point is a specific size?

Thanks 
-- 
View this message in context: http://old.nabble.com/Arrays-for-markersize--tp32848359p32848359.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

-- 
View this message in context: http://old.nabble.com/Arrays-for-markersize--tp32848328p32848328.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

Hi JD, 

I'm having exactly the same problem. Did you find a solution?

The only thing that I have noted so far is that when I plot for the second
time (when the axes start overlapping) if I move the cursor inside the
canvas area, it flickers and then the plots are displayed correctly. But it
only happens the first time.

Now, if you put a toolbar
self.toolbar = NavigationToolbar2TkAgg( self.canvas, self.PlotsContainer )

and you use any of the functions, say the zoom, then the flickering occurs
every time you pass over the white plotting area. The axes are updated (old
ones are gone) but the flickering is annoying. Plus you have to pretend you
want to zoom or something.

Besides that, I have been unsuccessful trying to tackle the issue.

Best,
johnmcpot
-- 
View this message in context: http://old.nabble.com/Clearing-the-axis-in-a-figure-embedded-in-Tkinter-tp32054762p32847767.html
Sent from the matplotlib - users mailing list archive at Nabble.com.

I'd love to see the compiler logs and try to fix what I can.  I don't 
have a Windows install to test, but maybe I can resolve the more obvious 
ones.

Mike

On 11/08/2011 05:49 AM, Mads Ipsen wrote:
> Hi,
>
> Thanks to the help from Christoph, I have been able to build 
> matplotlib-1.1.0 on both Win XP-32 and 64.
>
> I have noticed though, that quite a few warnings are produced when the 
> source is compiled. Is this something that the core developers would 
> like to fix, or is it a 'don't care' thing? If the info is useful, I'd 
> be happy to post it somewhere.
>
> Best regards,
>
> Mads
>
> -- 
> +-----------------------------------------------------+
> | Mads Ipsen                                          |
> +----------------------+------------------------------+
> | Gåsebæksvej 7, 4. tv |                              |
> | DK-2500 Valby        | phone:          +45-29716388 |
> | Denmark              | email:mad...@gm...  |
> +----------------------+------------------------------+
>
>
>
> ------------------------------------------------------------------------------
> RSA(R) Conference 2012
> Save $700 by Nov 18
> Register now
> http://p.sf.net/sfu/rsa-sfdev2dev1
>
>
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users


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

On Nov 14, 2011, at 5:34 PM, Volker Blum wrote:

> Thanks for the (two!) fast answers on the list. So there is hope :) I'll take a look at the fink internals, I guess. 
> best wishes
> Volker

having said that ... after trying the one piece of software that I need on another platform, here's what I get:

  File "[...]", line 84, in <module>
    length = norm(dot(rlatvec,end) - dot(rlatvec,start))
  File "/usr/lib64/python2.6/site-packages/matplotlib/mlab.py", line 1998, in norm
    raise NotImplementedError('Deprecated - see numpy.linalg.norm')
NotImplementedError: Deprecated - see numpy.linalg.norm

The script that I was trying to get to work worked fine on Ubuntu this summer. Where has "norm" gone? How can it have been deprecated? It looks like a matplotlib problem, hence I am asking here.

[I am also asking out of some curiosity - I am sure the problem can be fixed relatively easily, but what I am wondering is, am I looking at a problem that came with a new version of matplotlib, am I using too old a version of matplotlib?]

best wishes
Volker


> On Nov 14, 2011, at 5:15 PM, Jeff Blackburne wrote:
> 
>> 
>> On Nov 14, 2011, at 10:20 AM, Volker Blum wrote:
>> 
>>> ... just wanted to report this problem.
>>> 
>>> At the heart of the issue is the decision to have too many dependencies in matplotlib (which is why I am posting here). That, although viewed as good style, leads to an installation process that is, ultimately, practically impossible - except by buying a prepackaged solution. (which is possible but probably not the original intention)
>>> 
>>> What ultimately thwarts my installation attempts is the dependency on TeX. While a good thing in principle, most packaging tools do not realize that there is already a working TeX distribution there from another source, and will only accept their own - which, in the case of debian/fink, can no longer be postinstalled. It appears that I would have to uninstall and reinstall my entire pre-existing setup just to get matplotlib to work.
>>> 
>>> Has anyone seen this problem before? Is there a workaround?
>>> 
>>> best wishes
>>> Volker Blum
>> 
>> Hi Volker,
>> 
>> I have installed matplotlib with Fink. I had a similar issue, because I didn't need to GTKAgg backend and didn't want to install all of the GTK+ packages that were required. I ended up making my own fink package called matplotlib-py27-nogtk by editing the matplotlib-py.info and matplotlib-py.patch files in my /sw/fink/10.6/unstable/main/finkinfo/sci directory, to remove the dependencies and turn off the GTK+ check in setup.py, respectively. I put the resulting files in /sw/fink/10.6/local/main/finkinfo. You could try something like that, although it's kind of messy.
>> 
>> There may also be a "virtual" fink package for TeX that doesn't install anything, but counts as a proxy for a previous installation. If this is true, it's a much better solution that what I did.
>> 
>> I hope this helps. If you need more info, I suspect that your question is actually better suited for the fink-users list.
>> 
>> Good luck,
>> Jeff
>> 
> 
> 
> 
> 
> 
> ------------------------------------------------------------------------------
> RSA(R) Conference 2012
> Save $700 by Nov 18
> Register now
> http://p.sf.net/sfu/rsa-sfdev2dev1
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

Quote:
------------------------------------
matplotlib.pyplot.pcolor(*args, **kwargs)

Create a pseudocolor plot of a 2-D array.

C is the array of color values.
------------------------------------

I tried to see how can I map custom color values to example array, but
seems hard to understand.
I created 2x2 mesh, and appropriate C array for it. Changing values in
this C array changes colors on plotted mesh in what it seems irregular
way.

Does C array map colors from default colormap? If yes, in which way
they are plotted according values in this C array?
Or how can I tell matplotlib to use "this" RGB value for "this" cell
in a mesh, then another RGB value for other cell and so on


Thanks

> grid = AxesGrid(fig, 132,
>                 nrows_ncols = (3, 2),
>                 axes_pad = 0.1,
>                 cbar_location = "top",
>                 cbar_mode="single",
>                )

solved by using:

grid = AxesGrid(fig, 111,
                ...)


best regards, yoshi

Greetings.

I recently found myself in the position of needing to plot polar,
irregularly spaced data.  I've done similar using regularly spaced values
with no problem.  However, I've found that when the points become greatly
scattered, the triangulation does not translate from rectangular to polar
very well.  Below, find a code example that shows this; though it is much
"better" than my real-world case that uses simulation results.
 Essentially, in the translation from regular to polar axes, many of the
triangles overlap others, many features of the plot are lost, and the plot
looks mangled in certain regions, esp. across the theta=0 boundary.  While
subtle here (but MUCH worse in the results I'm trying to visualize), some
of the triangles lie outside of the triangulated region.  It isn't merely
that the polar plot is suffering from poor data coverage; the triangulation
is not working properly in polar coordinates and the results are
quantitatively different than the rectangular plot.

The obvious work-around for this problem illustrates the issue more
clearly.  If we convert rad, theta back to x, y and do a rectangular plot,
the triangulation is much better (not only is there no issue around
theta=0, but there are no overlapping triangles), all of the details of the
non-polar version are maintained, and the plot looks great.  This is not
the best solution, as polar plots in Matplotlib are quite elegant.

Any help here would be appreciated.  It could be that triangulations are
just not suited for polar plots; it could be that the theta=0 issue throws
things off, etc; I'm just not sure.  It would be perfect if I could use the
polar axes in the end.

Thanks.
-dw

#!/usr/bin/env python
'''
Demonstrate troubles with polar plots and triangulations.
'''
import numpy as np
import matplotlib.pyplot as plt

# Regular grid:
angle=np.linspace(0, 2*np.pi, 20)
x=np.tile(angle,20)
y=np.repeat(angle,20)
z=np.cos(x)*np.sin(y)

# Irregular grid:
x_ir=2*np.pi*np.random.random(400)
y_ir=2*np.pi*np.random.random(400)
z_ir=np.cos(x_ir)*np.sin(y_ir)

f=plt.figure()
a1=f.add_subplot(221)
a1.tricontourf(x,y,z); a1.plot(x,y, 'k+')
a2=f.add_subplot(222, polar=True)
a2.tricontourf(x,y,z); a2.plot(x,y, 'k+')
a2.triplot(x,y)

a3=f.add_subplot(223)
a3.tricontourf(x_ir,y_ir,z_ir); a3.plot(x_ir,y_ir, 'k+')
a4=f.add_subplot(224, polar=True)
a4.tricontourf(x_ir,y_ir,z_ir); a4.plot(x_ir,y_ir, 'k+')
a4.triplot(x_ir,y_ir)

# "Fix" back to rectangular.
x=y_ir*np.cos(x_ir)
y=y_ir*np.sin(x_ir)
f=plt.figure(); ax=f.add_subplot(111)
ax.tricontourf(x,y,z_ir)
ax.triplot(x,y)

Has ANYONE installed matplotlib on OSX 10.6 and had the module tests pass?  Specifically in a virtualenv setup?

-Dave

--
David Welch
dav...@gm...



On 11Nov, 2011, at 2:12 PM, David Welch wrote:

> Update: test folders are in the build directory, they are just not
> being copied during build.
> 
> *bump*
> 
> On 11/10/11, David Welch <dav...@gm...> wrote:
>> Hello,
>> 
>> I am installing matplotlib on Snow Leopard 10.6.  I downloaded v1.1.0 from
>> the sourceforge site and installed in this manner:
>> 
>> ############################
>> 
>> $ export CFLAGS="-arch i386 -arch x86_64 -I/usr/X11/include
>> -I/usr/X11/include/freetype2 -isysroot /Developer/SDKs/MacOSX10.6.sdk"
>> $ export LDFLAGS="-Wall -undefined dynamic_lookup -bundle -arch i386 -arch
>> x86_64 -L/usr/X11/lib -syslibroot,/Developer/SDKs/MacOSX10.6.sdk"
>> $ export FFLAGS="-arch i386 -arch x86_64"
>> $ tar -xf matplotlib-1.1.0.tar.gz
>> $ cd matplotlib-1.1.0
>> $ python setup.py build
>> $ python setup.py install
>> $
>> $ python
>>>>> import matplotlib as mpl
>>>>> mpl.test("1")
>> ...........EEEEEEEEEEE
>> ======================================================================
>> ERROR: Failure: AttributeError ('module' object has no attribute
>> 'test_backend_svg')
>> ----------------------------------------------------------------------
>> Traceback (most recent call last):
>>  File "/private/tmp/test/lib/python2.6/site-packages/nose/loader.py", line
>> 379, in loadTestsFromName
>>    module = resolve_name(addr.module)
>>  File "/private/tmp/test/lib/python2.6/site-packages/nose/util.py", line
>> 331, in resolve_name
>>    obj = getattr(obj, part)
>> AttributeError: 'module' object has no attribute 'test_backend_svg'
>> 
>> (etc.)
>> #############################
>> 
>> The failure is for all modules in matplotlib.tests except for test_agg,
>> test_cbook, test_mlab, and test_transform.
>> 
>> Is the sourceforge achive incomplete?
>> 
>> -Dave
>> 
>> --
>> David Welch
>> dav...@gm...
>> 
>> 
>> 
>> 
> 
> 
> -- 
> 
> Dept. of Psychiatry
> Dept. of Biomedical Engineering
> University of Iowa

Hi all,

This is my first time setting up matplotlib.

I'm on OS X Lion 10.7 (build 11A511s, so no updates done to the initial
release of OS X Lion).

I am using virtualenv and pip to do the installation.

I'm aware of the incompatibility with libpng 1.5, so I didn't just run "pip
install matplotlib"... instead...

I tried running this from inside the virtualenv:

"pip install -e git+
https://github.com/matplotlib/matplotlib#egg=matplotlib-dev"

Looks like it starts installing, but then I get this error:

/Users/myusername/.virtualenvs/nltk/lib/python2.7/site-packages/numpy/core/include/numpy/__multiarray_api.h:1532:
warning: ‘int _import_array()’ defined but not used

lipo: can't open input file:
/var/folders/wy/s1jr354d4xx7dk0lpdpbpsbc0000gn/T//ccfNUhyq.out (No such
file or directory)

error: command 'llvm-gcc-4.2' failed with exit status 1

----------------------------------------
Command /Users/sameerfx/.virtualenvs/nltk/bin/python -c "import setuptools;
__file__='/Users/sameerfx/.virtualenvs/nltk/src/matplotlib/setup.py';
exec(compile(open(__file__).read().replace('\r\n', '\n'), __file__,
'exec'))" develop --no-deps failed with error code 1
Storing complete log in /Users/sameerfx/.pip/pip.log

On Mon, Nov 14, 2011 at 6:11 AM, Michael Droettboom <md...@st...> wrote:
> This looks like a bug for the IPython folks.  If you make a file
> containing only "import gtk" and "%run" that file, one gets the same error.
>

Mmmh, I don't get the problem on ubuntu 10.10.  I'll try to check
later on an 11.10 machine I have.

To the OP: yes, this will be best discussed on the ipython list, since
it really has nothing to do with matplotlib.

Cheers,

f