matplotlib-users Mailing List for matplotlib (Page 12)

 Thanks Ernest, I had no idea that the DateFormatter was going to be treated
as latex as well.

However, escaping the \ with another \ did not worked.
I tried:

majorF = DateFormatter("\\n \\n %b")

How should I escape the \n ?


> majorF = DateFormatter("\n \n %b") # problem
>                          ^^  ^^
> A common mistake.
> You forgot to escape the "\" characters.
>
> Bye.
>
> Ernest
>

set_colorbar sets colorbar attribute. So I guess you can just check if
Mappable.colorbar is None or not.
Mappable.colorbar, when set, should be a tuple whose first item is an
image for colorbar and the second item is an colorbar axes.

Regards,

-JJ

On Tue, Feb 16, 2010 at 5:26 AM, Nico Schlömer <nic...@gm...> wrote:
> Alright, so I dug the sources a bit and found the snippet
>
> ========================== *snip* ==========================
>        cb = cbar.Colorbar(cax, mappable, **kw)
>
>        def on_changed(m):
>            #print 'calling on changed', m.get_cmap().name
>            cb.set_cmap(m.get_cmap())
>            cb.set_clim(m.get_clim())
>            cb.update_bruteforce(m)
>
>        self.cbid = mappable.callbacksSM.connect('changed', on_changed)
>        mappable.set_colorbar(cb, cax)
> ========================== *snap* ==========================
>
> I guess what happens is that a Colorbar is created, and a callback
> function registered which adapts this very color bar whenever there is
> a change in color maps/limits.
> Well. -- I reckon that means that at the moment there's no way to tell
> if a ScalarMappable has a color bar associated or not. :/ -- At least
> I don't see how it would be possible to dig up on_changed( ) from the
> list of callbacks and extract cb from it.
>
> Aaand everybody: "Fea-ture request, fea-ture request!"
> get_colorbar() for ScalarMappables :)
>
> Cheers,
> Nico
>
>
>
>
> On Mon, Feb 15, 2010 at 7:58 PM, Nico Schlömer <nic...@gm...> wrote:
>>> As far as I can see, it is the other way around, i.e., mappables
>>> (e.g., images) know about the colorbar they are connected.
>>
>> Well yeah, that'd be even better. I'll check out the API. -- Hints
>> would still be appreciated of course.
>>
>> --Nico
>>
>

15/02/10 @ 19:22 (-0500), thus spake Filipe Pires Alvarenga Fernandes:
> Hello list,
> 
> If I use DateFormatter with latex and lines breaks like this
> >>> DateFormatter("\n \n %b") I get an latex error:
> 
> http://pastebin.com/m5b186ded
> 
> Although, if I do not use the line breaks,
> >>> DateFormatter("%b")
> The problem disappears.
> 
> Below is a script that reproduces what I'm talking about:
> 
> #Example:
> from pylab            import *
> from matplotlib       import rcParams
> rcParams['text.usetex'] = True
> fig = figure()
> ax  = fig.add_subplot(111)
> fig.subplots_adjust(bottom=0.2)
> t = arange(100,110,.1)
> u = sin(t)
> v = cos(t)
> quiver([t],[[0]*len(t)],u,v)
> major  = DayLocator([10,04])
> minor  = DayLocator()
> majorF = DateFormatter("\n \n %b") # problem
                         ^^  ^^
A common mistake.
You forgot to escape the "\" characters.

Bye.

Ernest

Alright, so I dug the sources a bit and found the snippet

========================== *snip* ==========================
        cb = cbar.Colorbar(cax, mappable, **kw)

        def on_changed(m):
            #print 'calling on changed', m.get_cmap().name
            cb.set_cmap(m.get_cmap())
            cb.set_clim(m.get_clim())
            cb.update_bruteforce(m)

        self.cbid = mappable.callbacksSM.connect('changed', on_changed)
        mappable.set_colorbar(cb, cax)
========================== *snap* ==========================

I guess what happens is that a Colorbar is created, and a callback
function registered which adapts this very color bar whenever there is
a change in color maps/limits.
Well. -- I reckon that means that at the moment there's no way to tell
if a ScalarMappable has a color bar associated or not. :/ -- At least
I don't see how it would be possible to dig up on_changed( ) from the
list of callbacks and extract cb from it.

Aaand everybody: "Fea-ture request, fea-ture request!"
get_colorbar() for ScalarMappables :)

Cheers,
Nico




On Mon, Feb 15, 2010 at 7:58 PM, Nico Schlömer <nic...@gm...> wrote:
>> As far as I can see, it is the other way around, i.e., mappables
>> (e.g., images) know about the colorbar they are connected.
>
> Well yeah, that'd be even better. I'll check out the API. -- Hints
> would still be appreciated of course.
>
> --Nico
>

When I come back tonight I will try to fix the errors for you.

If you are interested in contributing to matplotlib check out this link:

http://matplotlib.sourceforge.net/faq/howto_faq.html#contributing-howto

The PDF is not the "original source", it's a product of the sphinx 
documentation system I think so contributing happens in simple plain text 
files. You can send a patch then.

Regards,
Philipp

Hi,

I'm trying to grid irregularly spaced data, such that the convex hull
of the data is not rectangular.  Specifically, all my data lies in an
equilateral triangle inside the unit circle.  I found:

     http://www.scipy.org/Cookbook/Matplotlib/Gridding_irregularly_spaced_data

and tried the suggested technique.  For my grid, I made a square of
the min and max of my data.  However, it had problems:

...
  File "/home/guest/.local/lib/python2.6/site-packages/matplotlib/delaunay/triangulate.py",
line 125, in _compute_convex_hull
    hull.append(edges.pop(hull[-1]))
KeyError: 0


Should I expect matplotlib.mlab.griddata to work with a dataset like
this?  I know that I can use hexbin, but it'd be really nice to see
contours explicitly.

<PH...@Ge...> wrote:

> ...maybe dividing the markers up into 2, 3, or 4 sections would be  
> useful too.
> ...

There's a gallery example doing that in general, making pie-charts out  
of the markers:

http://matplotlib.sourceforge.net/examples/api/scatter_piecharts.html

although I think my demo of it shows off its data-representation better:

# Piechart markers from matplotlib gallery, thanks to Manuel Metz for  
the original example
# CPHLewis, 2010.

import math
import numpy as np
import matplotlib.pyplot as plt

def payoff(x,y):
     return x*y*400

def outcome_xwins(x,y):
     return x/(x+y)

def outcome_ywins(x,y):
     return y/(x+y)

x_cases = [ .25, .5, .75]
y_cases = [ .33, .5, .66]
outcomes = [('x wins', outcome_xwins, 'blue'),
             ('y wins', outcome_ywins, 'green')] #the name,  
calculation, and plotting color for categories of outcome

fig = plt.figure()
ax = fig.add_subplot(111)
ax.set_title('Small multiples: pie charts calculated based on (x,y)')
legend_once = True
#At each point in the plot we calculate everything about the outcomes.
for x in x_cases:
     for y in y_cases:
         size = payoff(x,y)
         start_at = 0
         for result in outcomes:
             result_share = result[1](x,y)
             xpt = [0] + np.cos(np.linspace(2*math.pi*start_at,  
2*math.pi*(result_share+start_at), 10)).tolist()
             ypt = [0] + np.sin(np.linspace(2*math.pi*start_at,  
2*math.pi*(result_share+start_at), 10)).tolist()
             xypt = zip(xpt, ypt)
             ax.scatter([x],[y], marker = (xypt, 0), s = size,  
facecolor = result[2], label=result[0])
             start_at = start_at + result_share
         if legend_once: ax.legend() #don't know why this isn't  
picking up the labels.
         legend_once = False
plt.show()

On Mon, Feb 15, 2010 at 5:22 PM, John Hunter <jd...@gm...> wrote:
> Very nice and thorough work.  I think this should be included, but
> I'll wait to hear from other developers before committing.  Could you
> confirm that the unit tests pass?
>
>>>> import matplotlib
>>>> matplotlib.test()
>

Confirmed on rev 8133:

Ran 124 tests in 341.585s

FAILED (KNOWNFAIL=2, errors=2)

and the errors were something to do with hexbin extents and the figimage method.


> I think the markerangle would also be a useful contribution, though it
> would render some of the markers redundant (eg triangle left, right,
> etc, would all just be triangles with different angles...)
>

That was a concern I had as well, but I suppose > ^ v < (etc) could
just be considered shortcuts to particular angles.  Presumably, we
would not be removing them.  Correct?  Also, is the standard to have
the angle specified in degrees?  So what is more useful:  markerangle
or markerdeg?

The other difference is that when one specifies fillstyle='left', then
it would only apply to the marker at 0 degrees.  Whereas, marker='v',
fillstyle='left', markerangle=0  would correspond to marker='^',
fillstyle='right', markerangle=180   (or something like that).

On Mon, Feb 15, 2010 at 5:59 PM, T J <tj...@gm...> wrote:
> On Sun, Feb 14, 2010 at 2:49 PM, T J <tj...@gm...> wrote:
>> I ran across:
>>
>>    http://old.nabble.com/half-filled-markers-td24003576.html
>>
>> The name "fillstyle" can give the wrong impression about what is being
>> filled.  For example, see the comment here:
>>
>>   http://www.mail-archive.com/mat...@li.../msg13074.html
>>
>> It's probably too late, but would "markerfillstyle" be a better name for this?
>>
>> Also, the current implementation fills half of the marker with the
>> markerfacecolor and doesn't fill the marker at all for the other half.
>>  I think a neat (and simple) feature would be for users to specify two
>> colors.  Perhaps 'markerfacecolor2'.   The change to the code is
>> minimal, but the functionality it brings is quite flexible.
>> markerfacecolor2 can default to 'none' to maintain current
>> functionality.
>>
>> Should I file a ticket for this?



>>
>
> I went ahead and implemented this.  The user can now specify
> 'markercoloralt'.  In the process, I finished the "half-marker" code
> for all remaining filled_markers.   The diff is attached, which also
> includes a fix for bug #560720:
>
>    https://sourceforge.net/tracker/?func=detail&aid=2952236&group_id=80706&atid=560720
>
> Please comment.  If there are no comments in a few days, I'll file a ticket.
>
> A picture demonstrating this functionality is attached.  Demos for all
> filled markers can be obtained here:
>
>    http://www.filedropper.com/filledmarkers
>
> Note, the diff contains the script used to generate the pictures. More
> generally, I wonder if there should be a 'markerangle' keyword. I can
> probably push through and implement this, but I'd like to hear what
> people think about it.

Very nice and thorough work.  I think this should be included, but
I'll wait to hear from other developers before committing.  Could you
confirm that the unit tests pass?

>>> import matplotlib
>>> matplotlib.test()

I think the markerangle would also be a useful contribution, though it
would render some of the markers redundant (eg triangle left, right,
etc, would all just be triangles with different angles...)

Many thanks,
JDH

Hello list,

If I use DateFormatter with latex and lines breaks like this
>>> DateFormatter("\n \n %b") I get an latex error:

http://pastebin.com/m5b186ded

Although, if I do not use the line breaks,
>>> DateFormatter("%b")
The problem disappears.

Below is a script that reproduces what I'm talking about:

#Example:
from pylab            import *
from matplotlib       import rcParams
rcParams['text.usetex'] = True
fig = figure()
ax  = fig.add_subplot(111)
fig.subplots_adjust(bottom=0.2)
t = arange(100,110,.1)
u = sin(t)
v = cos(t)
quiver([t],[[0]*len(t)],u,v)
major  = DayLocator([10,04])
minor  = DayLocator()
majorF = DateFormatter("\n \n %b") # problem
#majorF = DateFormatter("%b") # no problem
minorF = DateFormatter('%d')
ax.xaxis.set_major_locator(major)
ax.xaxis.set_minor_locator(minor)
ax.xaxis.set_major_formatter(majorF)
ax.xaxis.set_minor_formatter(minorF)
gca().xaxis_date()
title(r"$\alpha \beta \gamma \delta$")
show()


I'm using the latest svn version with qt4 as backend.

Thanks, Filipe

I'm curious if anyone knows a good way to embed pydot
(http://code.google.com/p/pydot/) graphs (or really, any
graphviz-style graphs) inside matplotlib somehow.  I could easily
write out a png or something from pydot and then imshow it, but that
seems very kludgy.  Is there some way to load svg or other vector data
into matplotlib to be shown inside a figure?

TJ,

I think this current implementation and adding a marker rotation key word would be wonderful. When I get stuck doing GIS work, I end up using split markers very often. It's quite useful.

Now's probably not the time, but maybe dividing the markers up into 2, 3, or 4 sections would be useful too. 
But perhaps at that point it'd be easier to create half and quarter markers and then rotate accordingly as the user makes multiple calls to plot. I dunno...just thinking aloud.

This is a great contribution. Thanks a lot!
-paul

> -----Original Message-----
> From: T J [mailto:tj...@gm...]
> Sent: Monday, February 15, 2010 4:00 PM
> To: Matplotlib Users
> Subject: Re: [Matplotlib-users] half-filled markers, two-colors
> 
> On Sun, Feb 14, 2010 at 2:49 PM, T J <tj...@gm...> wrote:
> > I ran across:
> >
> >    http://old.nabble.com/half-filled-markers-td24003576.html
> >
> > The name "fillstyle" can give the wrong impression about what is being
> > filled.  For example, see the comment here:
> >
> >   http://www.mail-archive.com/matplotlib-
> us...@li.../msg13074.html
> >
> > It's probably too late, but would "markerfillstyle" be a better name
> for this?
> >
> > Also, the current implementation fills half of the marker with the
> > markerfacecolor and doesn't fill the marker at all for the other half.
> >  I think a neat (and simple) feature would be for users to specify two
> > colors.  Perhaps 'markerfacecolor2'.   The change to the code is
> > minimal, but the functionality it brings is quite flexible.
> > markerfacecolor2 can default to 'none' to maintain current
> > functionality.
> >
> > Should I file a ticket for this?
> >
> 
> I went ahead and implemented this.  The user can now specify
> 'markercoloralt'.  In the process, I finished the "half-marker" code
> for all remaining filled_markers.   The diff is attached, which also
> includes a fix for bug #560720:
> 
> 
> https://sourceforge.net/tracker/?func=detail&aid=2952236&group_id=80706&a
> tid=560720
> 
> Please comment.  If there are no comments in a few days, I'll file a
> ticket.
> 
> A picture demonstrating this functionality is attached.  Demos for all
> filled markers can be obtained here:
> 
>     http://www.filedropper.com/filledmarkers
> 
> Note, the diff contains the script used to generate the pictures. More
> generally, I wonder if there should be a 'markerangle' keyword. I can
> probably push through and implement this, but I'd like to hear what
> people think about it.

On Sun, Feb 14, 2010 at 2:49 PM, T J <tj...@gm...> wrote:
> I ran across:
>
>    http://old.nabble.com/half-filled-markers-td24003576.html
>
> The name "fillstyle" can give the wrong impression about what is being
> filled.  For example, see the comment here:
>
>   http://www.mail-archive.com/mat...@li.../msg13074.html
>
> It's probably too late, but would "markerfillstyle" be a better name for this?
>
> Also, the current implementation fills half of the marker with the
> markerfacecolor and doesn't fill the marker at all for the other half.
>  I think a neat (and simple) feature would be for users to specify two
> colors.  Perhaps 'markerfacecolor2'.   The change to the code is
> minimal, but the functionality it brings is quite flexible.
> markerfacecolor2 can default to 'none' to maintain current
> functionality.
>
> Should I file a ticket for this?
>

I went ahead and implemented this.  The user can now specify
'markercoloralt'.  In the process, I finished the "half-marker" code
for all remaining filled_markers.   The diff is attached, which also
includes a fix for bug #560720:

    https://sourceforge.net/tracker/?func=detail&aid=2952236&group_id=80706&atid=560720

Please comment.  If there are no comments in a few days, I'll file a ticket.

A picture demonstrating this functionality is attached.  Demos for all
filled markers can be obtained here:

    http://www.filedropper.com/filledmarkers

Note, the diff contains the script used to generate the pictures. More
generally, I wonder if there should be a 'markerangle' keyword. I can
probably push through and implement this, but I'd like to hear what
people think about it.

Tim Michelsen wrote:
> Hello,
> I have a similar problem to:
>> Suppose I plot a line from (0,0) to (1,1.5) to (2,2). Now I want to mark 
>> (1,1.5) with a green circle. How is that done?
> 

Your problem is not similar to the above; the problem above is solved 
with a simple call to "plot".

> I am performing a curve fit and also showing a distribution in my plot.
> In order to help the reader to evaluate the result I would like to draw certain
> boundaries (vertical and horizontal line).
> While I am aware on how to draw such lines, I would like to know wheather there
> are some functions in matplotlib which help me to retrieve the coordinates
> 
> a) at which two curves intersect
> b) at which a distribution reaches a certain value?
> 

I think this is strictly a computational problem, not a plotting 
problem, so I suggest you post the question to the numpy or scipy lists.

Eric

> Example:
> How do I get the y-axis value which is reached by the green curve in 
> http://matplotlib.sourceforge.net/_images/histogram_demo_extended_021.png
> a x-axis value of in 175?
> 
> I could proably use a solver from numpy like
> http://docs.scipy.org/doc/numpy/reference/generated/numpy.linalg.solve.html#numpy.linalg.solve
> but if I plot a distribution, the equation of the envelove is unknown at the
> first place.
> 
> I'd appreciate your help or pointers to examples.
> 
> Thanks a lot in advance,
> Timmie
> 
> 
> 
> ------------------------------------------------------------------------------
> SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
> Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
> http://p.sf.net/sfu/solaris-dev2dev
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html; charset=ISO-8859-1"
 http-equiv="Content-Type">
</head>
<body bgcolor="#ffffff" text="#000000">
Well, I looked at the links, and only one that seemed right for this
was the first one. I found this:<br>
<br>
If not, please provide the following information in your e-mail to the
<a class="reference external"
 href="http://lists.sourceforge.net/mailman/listinfo/matplotlib-users">mailing
list</a>:<br>
<br>
So here's my report. Mostly spelling errors. See attached. I have no
way of marking it up, but the problem is simple. About 7 or so places
misuse the word axes.&nbsp; On page 199 of the same document, five lines
down, it says ," does not want to redrawing". "redraw". That's it. The
list of 5 commands below it, leave me puzzled. Question marks, for one.
<br>
<br>
That's it. <br>
<br>
<br>
On 2/13/2010 6:58 PM, John Hunter wrote:
<blockquote
 cite="mid:88e...@ma..."
 type="cite">
  <pre wrap="">On Sat, Feb 13, 2010 at 6:44 AM, Wayne Watson
<a class="moz-txt-link-rfc2396E" href="mailto:sie...@sb...">&lt;sie...@sb...&gt;</a> wrote:
  </pre>
  <blockquote type="cite">
    <pre wrap="">In this case, it's spelling errors, mostly. axes for axis, etc.
    </pre>
  </blockquote>
  <pre wrap="">
<a class="moz-txt-link-freetext" href="http://matplotlib.sourceforge.net/faq/troubleshooting_faq.html#report-a-problem">http://matplotlib.sourceforge.net/faq/troubleshooting_faq.html#report-a-problem</a>

<a class="moz-txt-link-freetext" href="http://matplotlib.sourceforge.net/faq/howto_faq.html#contributing-howto">http://matplotlib.sourceforge.net/faq/howto_faq.html#contributing-howto</a>

<a class="moz-txt-link-freetext" href="http://matplotlib.sourceforge.net/faq/howto_faq.html#contribute-to-matplotlib-documentation">http://matplotlib.sourceforge.net/faq/howto_faq.html#contribute-to-matplotlib-documentation</a>

JDH

  </pre>
</blockquote>
<br>
<div class="moz-signature">-- <br>
"Crime is way down. War is declining. And that's far from the good
news." -- Steven Pinker (and other sources)
Why is this true, but yet the media says otherwise? The media
knows very well how to manipulate us (see limbic, emotion, $$). -- WTW</div>
</body>
</html>

Hi Nico,
I'm pretty sure the functionality is buried in there but unfortunately I 
couldn't figure out how to put it into the imsave function, so for now I 
think you have to resort to using PIL to do this.
Gary R.

Nico Schlömer wrote:
> Hi,
> 
> I see that with imsave() it's possible to save an image based on its
> cmap. Is there also functionality in matplotlib to to store a file
> based on RGB(alpha) information?
> 
> Cheers,
> Nico

Hi,

I am trying to develop an application that I can run inside the ipython 
shell.  One of my methods creates a plot, asks the user to make a choice 
based on that plot, and then creates another plot that displays the chosen 
set of information.

If the choices are made with a qt or wx dialogue, everything goes fine.  If 
I try to get the choice by asking the user to type the information into the 
shell, neither plot appears until after the choice is made.

I have tried show() and draw() but neither make any difference.

thanks for any help

Ken Dere

Yes, yes!

what he said...
Thanks a lot JJ.

Dear developers, would it make sense to have
setp(axes1.get_xticklabels(), visible=False)
also automatically set
axes1.xaxis.offsetText.set_visible(False)
?

Cheers,
    Jan


On Mon, Feb 15, 2010 at 5:10 PM, Jae-Joon Lee <lee...@gm...> wrote:

> Try
>
> ax1.xaxis.offsetText.set_visible(False)
>
> where ax1 is the upper axes.
>
> Regards,
>
> -JJ
>
>
> On Mon, Feb 15, 2010 at 4:50 AM, Jan Strube <cur...@gm...> wrote:
> > Hi Jeff,
> > thanks for your quick reply.
> > Unfortunately, the line you sent me doesn't have any effect on the plot,
> > either before or after turning off the tick labels.
> > Do you have another suggestion?
> > Cheers,
> >     Jan
> > On Sun, Feb 14, 2010 at 11:28 PM, Jeffrey Blackburne <je...@mi...>
> wrote:
> >>
> >> On Feb 14, 2010, at 5:41 PM, Jan Strube wrote:
> >>
> >>> Dear matplotters,
> >>>
> >>> I'm trying to follow
> >>>
> >>>
> http://matplotlib.sourceforge.net/examples/pylab_examples/ganged_plots.html
> >>> as an example how to turn of the ticks in the case of shared x axes.
> >>> The tick labels are gone, but unfortunately, matplotlib still plots a
> >>> '1e5' on the axis for which I have turned off the tick labels.
> >>> Please see the attached file for the problem
> >>>
> >>> How can I also switch of the exponent?
> >>>
> >>> Thanks,
> >>>    Jan
> >>
> >>
> >> Try this:
> >>
> >>
> ax.xaxis.set_major_formatter(mpl.ticker.ScalarFormatter(useOffset=False))
> >>
> >> where 'ax' is the name of the top subplot.
> >>
> >> Good luck,
> >> Jeff
> >>
> >
> >
> >
> ------------------------------------------------------------------------------
> > SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
> > Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
> > http://p.sf.net/sfu/solaris-dev2dev
> > _______________________________________________
> > Matplotlib-users mailing list
> > Mat...@li...
> > https://lists.sourceforge.net/lists/listinfo/matplotlib-users
> >
> >
>

All,

This error:
The debugged program raised the exception unhandled AttributeError
"'FigureCanvasMac' object has no attribute 'buffer_rgba'"
File: /Users/darnold/Documents/temp/Matplotlib/PylabExamples/agg_buffer_to_array.py, Line: 16
is raised by the following script on my Macbook.

# agg_buffer_to_array.py
 
import matplotlib
matplotlib.use('macosx')
from pylab import figure, show
import numpy as np

# make an agg figure
fig = figure()
ax = fig.add_subplot(111)
ax.plot([1,2,3])
ax.set_title('a simple figure')
fig.canvas.draw()

# grab rhe pixel buffer and dumpy it into a numpy array
buf = fig.canvas.buffer_rgba(0,0)
l, b, w, h = fig.bbox.bounds
X = np.fromstring(buf, np.uint8)
X.shape = h,w,4

# now display the array X as an Axes in a new figure
fig2 = figure()
ax2 = fig2.add_subplot(111, frameon=False)
ax2.imshow(X)
show()

This is captured from:  http://matplotlib.sourceforge.net/examples/pylab_examples/agg_buffer_to_array.html

With:

matplotlib.use('Agg')

Nothing happens at all. With --verbose-helpful, yields the following:

$HOME=/Users/darnold
CONFIGDIR=/Users/darnold/.matplotlib
matplotlib data path /Library/Frameworks/Python.framework/Versions/6.0.0/lib/python2.6/site-packages/matplotlib/mpl-data
loaded rc file /Users/darnold/.matplotlib/matplotlibrc
matplotlib version 0.99.1.1
verbose.level helpful
interactive is False
units is False
platform is darwin
Using fontManager instance from /Users/darnold/.matplotlib/fontList.cache
backend agg version v2.2
findfont: Matching :family=sans-serif:style=normal:variant=normal:weight=normal:stretch=normal:size=medium to Bitstream Vera Sans (/Library/Frameworks/Python.framework/Versions/4.3.0/lib/python2.5/site-packages/matplotlib-0.98.5.2n2-py2.5-macosx-10.3-fat.egg/matplotlib/mpl-data/fonts/ttf/Vera.ttf) with score of 0.000000
findfont: Matching :family=sans-serif:style=normal:variant=normal:weight=normal:stretch=normal:size=large to Bitstream Vera Sans (/Library/Frameworks/Python.framework/Versions/4.3.0/lib/python2.5/site-packages/matplotlib-0.98.5.2n2-py2.5-macosx-10.3-fat.egg/matplotlib/mpl-data/fonts/ttf/Vera.ttf) with score of 0.000000

Both

matplotlib.use('tkagg')

and

matplotlib.use('wxagg')

work as they should.

David.

> As far as I can see, it is the other way around, i.e., mappables
> (e.g., images) know about the colorbar they are connected.

Well yeah, that'd be even better. I'll check out the API. -- Hints
would still be appreciated of course.

--Nico

On Sun, Feb 14, 2010 at 10:36 PM, David Arnold <dwa...@su...>wrote:

> All,
>
> This example:
> http://matplotlib.sourceforge.net/examples/event_handling/keypress_demo.html
>
> Raises this exception o my Macbook when the key 's' is pressed:
>
> The debugged program raised the exception unhandled TypeError
> "save_figure() takes exactly 1 argument (2 given)"
> File:
> /Library/Frameworks/Python.framework/Versions/6.0.0/lib/python2.6/site-packages/matplotlib/backend_bases.py,
> Line: 1703
>

I had reported this "s" key-handling issue before at
http://old.nabble.com/Assigning-%22k%22-key-for-xscaling-td27262672.html

(By the way, I and Matthias expanding the key-handling functionality a
little bit further -configuring and deassigning keys etc... Maybe by means
of this e-mail someone can review the patch at that mail and apply to the
trunk)

And yes I am getting a similar error when I hit "s" using Qt4Agg backend on
MPL svn8105

I[1]: plt.plot(range(10))
O[1]: [<matplotlib.lines.Line2D object at 0x9fa096c>]

I[2]:
---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)

/home/gsever/Desktop/python-repo/matplotlib/lib/matplotlib/backends/backend_qt4.pyc
in keyPressEvent(self, event)
    150     def keyPressEvent( self, event ):
    151         key = self._get_key( event )
--> 152         FigureCanvasBase.key_press_event( self, key )
    153         if DEBUG: print 'key press', key
    154

/home/gsever/Desktop/python-repo/matplotlib/lib/matplotlib/backend_bases.pyc
in key_press_event(self, key, guiEvent)
   1290         s = 'key_press_event'
   1291         event = KeyEvent(s, self, key, self._lastx, self._lasty,
guiEvent=guiEvent)
-> 1292         self.callbacks.process(s, event)
   1293
   1294     def key_release_event(self, key, guiEvent=None):

/home/gsever/Desktop/python-repo/matplotlib/lib/matplotlib/cbook.pyc in
process(self, s, *args, **kwargs)
    167         self._check_signal(s)
    168         for func in self.callbacks[s].values():
--> 169             func(*args, **kwargs)
    170
    171

/home/gsever/Desktop/python-repo/matplotlib/lib/matplotlib/backend_bases.pyc
in key_press(self, event)
   1890             self.canvas.toolbar.zoom()
   1891         elif event.key == s:
-> 1892             self.canvas.toolbar.save_figure(self.canvas.toolbar)
   1893
   1894         if event.inaxes is None:

TypeError: save_figure() takes exactly 1 argument (2 given)

[gsever@ccn various]$ python sysinfo.py
================================================================================
Platform     :
Linux-2.6.31.9-174.fc12.i686.PAE-i686-with-fedora-12-Constantine
Python       : ('CPython', 'tags/r262', '71600')
IPython      : 0.10
NumPy        : 1.5.0.dev8038
Matplotlib   : 1.0.svn (python setupegg.py develop newer shows
matplotlib.__version__ correctly :)
================================================================================

Thanks.


>
> David
>
> ------------------------------------------------------------------------------
> SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
> Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
> http://p.sf.net/sfu/solaris-dev2dev
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>



-- 
Gökhan

On Mon, Feb 15, 2010 at 12:25 PM, Nico Schlömer
<nic...@gm...> wrote:
> Well, it's related to the TikZ converter I'm writing. After having
> created the plot, the script is of course totally oblivious to what
> exact commands were used.
> I was thinking that there is still some sort of bond between the color
> bar and its parent plot after their creation, e.g., for when the color
> map of the main plot is changed. -- Is that not the case?

I doubt it.
As far as I can see, it is the other way around, i.e., mappables
(e.g., images) know about the colorbar they are connected. But I hope
some other developers can confirm (or dispute) this.
For this kind of work, you need to understand some of internals of
matplotlib, and I recommend you to go through the matplotlib sources.

Regards,

-JJ

>
>  --Nico
>
>
>
> On Mon, Feb 15, 2010 at 6:16 PM, Jae-Joon Lee <lee...@gm...> wrote:
>> Is there any reason that you need to find out which axes is a color
>> bar axes from the list of axes? Can you just keep references to
>> colorbars you create?
>>
>> cbar = colorbar()
>> cax = cbar.ax
>>
>> cax is the axes instance of the colobar you just created.
>>
>> Regards,
>>
>> -JJ
>>
>>
>> On Mon, Feb 15, 2010 at 12:04 PM, Nico Schlömer
>> <nic...@gm...> wrote:
>>> Hi,
>>>
>>> when plotting a color bar with a plot in matplotlib, the color bar
>>> gets treated internally as Axes.
>>>
>>> With two main plots, each of which comes with a color bar, one structurally gets
>>>
>>> <class 'matplotlib.figure.Figure'>
>>>    <class 'matplotlib.axes.Axes'>
>>>    <class 'matplotlib.axes.Axes'>
>>>    <class 'matplotlib.axes.Axes'>
>>>    <class 'matplotlib.axes.Axes'>
>>>
>>> (that is, a Figure has for childres Axes). To find out which one of
>>> those is a color bar, I basically inspect their children an look for
>>> Arrays with shape (256,), which is what color bars look like. That's
>>> ugly of course, but it kind of works(tm). :)
>>>
>>> I'm having problems, though, with associating color bars with the
>>> specific plot. Can I rely on the rule that an Axes -- if it has a
>>> color bar --, is immediately followed by the corresponding (color bar)
>>> Axes environment? Are there any other properties I could check to
>>> identify color bars? (Tried get_label to no avail.)
>>>
>>> Cheers,
>>> Nico
>>>
>>> ------------------------------------------------------------------------------
>>> SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
>>> Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
>>> http://p.sf.net/sfu/solaris-dev2dev
>>> _______________________________________________
>>> Matplotlib-users mailing list
>>> Mat...@li...
>>> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>>>
>>
>

I cannot reproduce this error both with 0.99.1 maintenance branch and
the current svn (with GtkAgg backend).
What version of matplotlib and what backend are you using?

http://matplotlib.sourceforge.net/faq/troubleshooting_faq.html

Regards,

-JJ


On Sun, Feb 14, 2010 at 11:36 PM, David Arnold
<dwa...@su...> wrote:
> All,
>
> This example:  http://matplotlib.sourceforge.net/examples/event_handling/keypress_demo.html
>
> Raises this exception o my Macbook when the key 's' is pressed:
>
> The debugged program raised the exception unhandled TypeError
> "save_figure() takes exactly 1 argument (2 given)"
> File: /Library/Frameworks/Python.framework/Versions/6.0.0/lib/python2.6/site-packages/matplotlib/backend_bases.py, Line: 1703
>
> David
> ------------------------------------------------------------------------------
> SOLARIS 10 is the OS for Data Centers - provides features such as DTrace,
> Predictive Self Healing and Award Winning ZFS. Get Solaris 10 NOW
> http://p.sf.net/sfu/solaris-dev2dev
> _______________________________________________
> Matplotlib-users mailing list
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-users
>

On Mon, Feb 15, 2010 at 2:32 AM, rcnelson <rne...@gm...> wrote:
> 1) Are there any plans or would it make sense to add another keyword to the
> pyplot.arrow function that allows you to choose the arrow class you would
> like to use? The default could be FancyArrow so that the original usage of
> pyplot.arrow will not be affected. The axes.arrow function - which it looks
> like it gets called by the pyplot.arrow function - could then convert the
> input arguments into the form necessary for the class you choose.
>

I recommend you to use "annotate" (see below). Because most of these
things are already addressed by "annotate", I don't see any immediate
need to enhance "arrow". But maybe it would be a good idea to mention
about "annotate" in the "arrow" documentation and vice versa.

> 2) Or... Is there a simple way that you can call the arrow function with
> start and end points in data coordinates, but have the arrow parameters
> calculated in normalized figure coordinates? I think FancyArrow calculates
> the head and body points using a line perpendicular to the line of the arrow
> in data coordinates, which I think is the source of my problem (? -- at
> least that is what I found doing some test calculations on my own). However,
> if I call the pyplot.arrow function with the following keywords,
> 'trasform=fig.transFigure, figure=fig' (as per the Artist tutorial, see
> below), then the arrow looks okay, but it needs to be positioned in
> normalized figure coordinates and it does not move when you zoom or
> translate the plot.
>

I guess you can just use "annotate" (with empty string) for your
purpose. See the the example below.

http://matplotlib.sourceforge.net/users/annotations_guide.html#annotating-with-arrow

Let me know if it does not fits your need.

Regards,

-JJ