You can subscribe to this list here.
2003 
_{Jan}

_{Feb}

_{Mar}

_{Apr}

_{May}
(3) 
_{Jun}

_{Jul}

_{Aug}
(12) 
_{Sep}
(12) 
_{Oct}
(56) 
_{Nov}
(65) 
_{Dec}
(37) 

2004 
_{Jan}
(59) 
_{Feb}
(78) 
_{Mar}
(153) 
_{Apr}
(205) 
_{May}
(184) 
_{Jun}
(123) 
_{Jul}
(171) 
_{Aug}
(156) 
_{Sep}
(190) 
_{Oct}
(120) 
_{Nov}
(154) 
_{Dec}
(223) 
2005 
_{Jan}
(184) 
_{Feb}
(267) 
_{Mar}
(214) 
_{Apr}
(286) 
_{May}
(320) 
_{Jun}
(299) 
_{Jul}
(348) 
_{Aug}
(283) 
_{Sep}
(355) 
_{Oct}
(293) 
_{Nov}
(232) 
_{Dec}
(203) 
2006 
_{Jan}
(352) 
_{Feb}
(358) 
_{Mar}
(403) 
_{Apr}
(313) 
_{May}
(165) 
_{Jun}
(281) 
_{Jul}
(316) 
_{Aug}
(228) 
_{Sep}
(279) 
_{Oct}
(243) 
_{Nov}
(315) 
_{Dec}
(345) 
2007 
_{Jan}
(260) 
_{Feb}
(323) 
_{Mar}
(340) 
_{Apr}
(319) 
_{May}
(290) 
_{Jun}
(296) 
_{Jul}
(221) 
_{Aug}
(292) 
_{Sep}
(242) 
_{Oct}
(248) 
_{Nov}
(242) 
_{Dec}
(332) 
2008 
_{Jan}
(312) 
_{Feb}
(359) 
_{Mar}
(454) 
_{Apr}
(287) 
_{May}
(340) 
_{Jun}
(450) 
_{Jul}
(403) 
_{Aug}
(324) 
_{Sep}
(349) 
_{Oct}
(385) 
_{Nov}
(363) 
_{Dec}
(437) 
2009 
_{Jan}
(500) 
_{Feb}
(301) 
_{Mar}
(409) 
_{Apr}
(486) 
_{May}
(545) 
_{Jun}
(391) 
_{Jul}
(518) 
_{Aug}
(497) 
_{Sep}
(492) 
_{Oct}
(429) 
_{Nov}
(357) 
_{Dec}
(310) 
2010 
_{Jan}
(371) 
_{Feb}
(657) 
_{Mar}
(519) 
_{Apr}
(432) 
_{May}
(312) 
_{Jun}
(416) 
_{Jul}
(477) 
_{Aug}
(386) 
_{Sep}
(419) 
_{Oct}
(435) 
_{Nov}
(320) 
_{Dec}
(202) 
2011 
_{Jan}
(321) 
_{Feb}
(413) 
_{Mar}
(299) 
_{Apr}
(215) 
_{May}
(284) 
_{Jun}
(203) 
_{Jul}
(207) 
_{Aug}
(314) 
_{Sep}
(321) 
_{Oct}
(259) 
_{Nov}
(347) 
_{Dec}
(209) 
2012 
_{Jan}
(322) 
_{Feb}
(414) 
_{Mar}
(377) 
_{Apr}
(179) 
_{May}
(173) 
_{Jun}
(234) 
_{Jul}
(151) 
_{Aug}

_{Sep}

_{Oct}

_{Nov}

_{Dec}

S  M  T  W  T  F  S 





1
(5) 
2
(24) 
3
(2) 
4

5
(4) 
6
(1) 
7
(22) 
8
(9) 
9
(23) 
10
(6) 
11

12
(7) 
13
(17) 
14
(12) 
15
(10) 
16
(22) 
17
(11) 
18
(6) 
19
(11) 
20
(13) 
21
(10) 
22
(7) 
23
(7) 
24
(5) 
25
(3) 
26
(20) 
27
(17) 
28
(25) 
29
(16) 
30
(17) 
31
(8) 
From: Jack Sankey <jack.sankey@gm...>  20070309 22:44:55

Hello, When I plot using the errorbar() routine, I get beautiful plots, complete with error bars. Then, when I want to perform manipulations on the data after the fact, I use lines = axes.get_lines() to get at the lines lines[n].get_xdata() and set_xdata() to edit the data etc... The problem is when I do errobar() I get not only the data lines, but also a bunch of small lines for drawing the error bars, and it's very difficult to sort them all out to get at the data of the plot. My question is, is there an easy/bulletproof way to tell if a given line from get_lines() is an error bar or the actual data? Thanks! Jack 
From: Eric Firing <efiring@ha...>  20070309 21:23:57

Suresh Pillai wrote: > I guess I didn't read the following carefully: > > "... The aspect ratio of the figure window is that of the array > ... Because of how matshow() tries to > set the figure aspect ratio to be the one of the array, ..." > > which would explain the behaviour below. > > Why the restrictions? Seems one would want to put colorbars, etc in the > same figure and so why not behave like imshow() which it calls to make the > output. And why the new figure (so no possibility of subplots or > overlays)? Just curious ... I guess I will use imshow() directly and > modify the axes as suggested before to get the output looking like > matshow() > Suresh, I think the general answer to your questions is "historical accident". Matshow was contributed a long time ago, and has been updated only minimally to take into account changes made elsewhere. There was even a suggestion that it might not be needed any more, but I think that it can continue to be useful and is worth updating to be an axes method, etc. This is on my growing mental list of things to do, and is probably one of the easier ones. Eric > Cheers, > Suresh > > On Thu, 8 Mar 2007, Suresh Pillai wrote: > >> If one inserts a colorbar after using matshow, then the matrix plot's aspect >> ratio is incorrect altered. Here are 2 cases to compare >> >> import pylab >> matrix = pylab.rand(30,30) >> >> 1) matshow() before colorbar() >> >> pylab.matshow(matrix) >> pylab.colorbar() >> pylab.show() >> >> The matrix plot is squished in the xdirection while not in the y thus losing >> its proper aspect ratio (equal by default). >> >> 2) imshow() before colorbar() >> >> pylab.imshow(matrix) >> pylab.colorbar() >> pylab.show() >> >> Everthing is okay in this case. >> >> >> Thanks, >> Suresh >> >> > >  > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveysand earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Matplotlibusers mailing list > Matplotlibusers@... > https://lists.sourceforge.net/lists/listinfo/matplotlibusers 
From: <jks@ik...>  20070309 20:35:18

Suresh Pillai <stochashtic@...> writes: > I discovered the same problem, so I went looking and found the mailing > list properly archived at nabble.com: Another useful mailing list archive is gmane.org: http://dir.gmane.org/gmane.comp.python.matplotlib.general http://dir.gmane.org/gmane.comp.python.matplotlib.devel  Jouni K. Seppänen http://www.iki.fi/jks 
From: <jks@ik...>  20070309 20:34:16

Jeff Peery <jeffpeery@...> writes: > hello, I have an application I'm working on, and I need to remove > figtext() without using a figure.clear(). how can I do this? thanks. When you call figtext, save the return value, and then call set_visible(False) on it to hide it, or delete it from the figure's texts list: ft=fig.figtext(x, y, text) # ... ft.set_visible(False); draw() # or: fig.texts.remove(ft); draw()  Jouni K. Seppänen http://www.iki.fi/jks 
From: Andrew Straw <strawman@as...>  20070309 18:47:48

set markerfacecolor (a.k.a. mfc) = 'None' (make sure you include the quotes). Andrew John T Whelan wrote: > Dear matplotlib gurus, > > When I use > > plot(t,x,'rx',t,y,'bs'); > > in matlab, it produces blue boxes for y, i.e., squares with a blue > border and a transparent interior, so that if one of them lies on top > of a red x, I can see the red x inside the blue box. The same > construction in matplotlib produces blue squares: squares with a black > border and a blue interior. I can change the color of the interior > with the markerfacecolor or mfc argument, e.g., > > plot(t,x,'rx'); > plot(t,y,'bs',mec='b',mfc='w'); > > but that produces an opaque white interior which renders invisible any > red x it covers up. > > I can change the transparency of a line with the alpha argument, but > there seems to be no corresponding markerfacealpha. > > Is there a way in matplotlib to get a square marker with a blue border > and a transparent interior? > > Thanks, > 
From: John T Whelan <john.whelan@li...>  20070309 17:57:58

Dear matplotlib gurus, When I use plot(t,x,'rx',t,y,'bs'); in matlab, it produces blue boxes for y, i.e., squares with a blue border and a transparent interior, so that if one of them lies on top of a red x, I can see the red x inside the blue box. The same construction in matplotlib produces blue squares: squares with a black border and a blue interior. I can change the color of the interior with the markerfacecolor or mfc argument, e.g., plot(t,x,'rx'); plot(t,y,'bs',mec='b',mfc='w'); but that produces an opaque white interior which renders invisible any red x it covers up. I can change the transparency of a line with the alpha argument, but there seems to be no corresponding markerfacealpha. Is there a way in matplotlib to get a square marker with a blue border and a transparent interior? Thanks,  ====================================================================== Office: 0.17 (Golm) Dr. John T. Whelan Phone: +49 331 567 7117 MPI for Gravitational Physics FAX: +49 331 567 7298 (AlbertEinstein Institute) http://www.aei.mpg.de/~whelan/ D14424 Potsdam john.whelan@... john.whelan@... ====================================================================== 
From: Suresh Pillai <stochashtic@ya...>  20070309 17:55:16

I guess I didn't read the following carefully: "... The aspect ratio of the figure window is that of the array ... Because of how matshow() tries to set the figure aspect ratio to be the one of the array, ..." which would explain the behaviour below. Why the restrictions? Seems one would want to put colorbars, etc in the same figure and so why not behave like imshow() which it calls to make the output. And why the new figure (so no possibility of subplots or overlays)? Just curious ... I guess I will use imshow() directly and modify the axes as suggested before to get the output looking like matshow() Cheers, Suresh On Thu, 8 Mar 2007, Suresh Pillai wrote: > If one inserts a colorbar after using matshow, then the matrix plot's aspect > ratio is incorrect altered. Here are 2 cases to compare > > import pylab > matrix = pylab.rand(30,30) > > 1) matshow() before colorbar() > > pylab.matshow(matrix) > pylab.colorbar() > pylab.show() > > The matrix plot is squished in the xdirection while not in the y thus losing > its proper aspect ratio (equal by default). > > 2) imshow() before colorbar() > > pylab.imshow(matrix) > pylab.colorbar() > pylab.show() > > Everthing is okay in this case. > > > Thanks, > Suresh > > 
From: Perry Greenfield <perry@st...>  20070309 17:11:34

We are looking for someone to fill a position at the Space Telescope Science Institute (in Baltimore, MD) to work on Python tools for astronomical data processing and analysis. Details can be found at: http://www.stsci.edu/institute/brc/hr/co/external/Req559.html 
From: Suresh Pillai <stochashtic@ya...>  20070309 15:24:06

I discovered the same problem, so I went looking and found the mailing list properly archived at nabble.com: http://www.nabble.com/Creatinganonlinearcolormap.t3362841.html Cheers, Suresh On Fri, 9 Mar 2007, Ken McIvor wrote: > On Mar 9, 2007, at 5:11 AM, Uwe Schmitt wrote: >> >> Thanks, but I can not access this article from the mailing lists >> archive. >> On sourceforge the newest posting is from 23th feb. > > I'm not sure what the problem with SourceForge is. I'll forward you > that email offlist. > > Ken > > >  > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveysand earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Matplotlibusers mailing list > Matplotlibusers@... > https://lists.sourceforge.net/lists/listinfo/matplotlibusers > 
From: Matthieu Brucher <matthieu.brucher@gm...>  20070309 14:51:40

Thank you, I think thatthis will solve my problem :) I didn't know this class existed. Matthieu 2007/3/9, John Hunter <jdh2358@...>: > > On 3/9/07, Matthieu Brucher <matthieu.brucher@...> wrote: > > > What I have is a set of points in a numpy.array  for instance size > (2000, > > 2) . What I have as well is a nump.array of size (2000, 3). How can I > make > > plot understand that each line of the set points must be painted with > the > > corresponding line in the colour array ? > > You'll probably want to use a regular poly collection, as in the > example below. Your array of facecolors can pretty much be whatever > you want: > > from pylab import figure, nx, show, cm > from matplotlib.collections import RegularPolyCollection > > > fig = figure() > ax = fig.add_subplot(111) > > offsets = nx.mlab.rand(20,2) > facecolors = [cm.jet(x) for x in nx.mlab.rand(20)] > black = (0,0,0,1) > > collection = RegularPolyCollection( > fig.dpi, > numsides=5, # a pentagon > rotation=0, > sizes=(50,), > facecolors = facecolors, > edgecolors = (black,), > linewidths = (1,), > offsets = offsets, > transOffset = ax.transData, > ) > > ax.add_collection(collection) > > show() > > > > > > > > > Matthieu > > > > >  > > Take Surveys. Earn Cash. Influence the Future of IT > > Join SourceForge.net's Techsay panel and you'll get the chance to share > your > > opinions on IT & business topics through brief surveysand earn cash > > > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > > _______________________________________________ > > Matplotlibusers mailing list > > Matplotlibusers@... > > https://lists.sourceforge.net/lists/listinfo/matplotlibusers > > > > > 
From: John Hunter <jdh2358@gm...>  20070309 14:30:44

On 3/9/07, Matthieu Brucher <matthieu.brucher@...> wrote: > What I have is a set of points in a numpy.array  for instance size (2000, > 2) . What I have as well is a nump.array of size (2000, 3). How can I make > plot understand that each line of the set points must be painted with the > corresponding line in the colour array ? You'll probably want to use a regular poly collection, as in the example below. Your array of facecolors can pretty much be whatever you want: from pylab import figure, nx, show, cm from matplotlib.collections import RegularPolyCollection fig = figure() ax = fig.add_subplot(111) offsets = nx.mlab.rand(20,2) facecolors = [cm.jet(x) for x in nx.mlab.rand(20)] black = (0,0,0,1) collection = RegularPolyCollection( fig.dpi, numsides=5, # a pentagon rotation=0, sizes=(50,), facecolors = facecolors, edgecolors = (black,), linewidths = (1,), offsets = offsets, transOffset = ax.transData, ) ax.add_collection(collection) show() > Matthieu > >  > Take Surveys. Earn Cash. Influence the Future of IT > Join SourceForge.net's Techsay panel and you'll get the chance to share your > opinions on IT & business topics through brief surveysand earn cash > http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV > _______________________________________________ > Matplotlibusers mailing list > Matplotlibusers@... > https://lists.sourceforge.net/lists/listinfo/matplotlibusers > > 
From: Matthieu Brucher <matthieu.brucher@gm...>  20070309 14:19:09

> > Complete examples always help ince we have no way of knowing what the > points data structures look like, but I'll hazard a gues. The x and y > arguments to "plot" need to be sequences. Ie, something like > > plot([0.5], [0.5], 'ro') > > It can be inefficient to plot many separate points this way  if you > have a lot of points, use a > matplotlib.collections.RegularPolyCollection or scatter. > Thank you for your answer :) OK, I'll try to wrap them :. The best solution would indeed be to paint them all at once, but I didn't manage to do that, even when I looked in the scatter_demo2 example :( What I have is a set of points in a numpy.array  for instance size (2000, 2) . What I have as well is a nump.array of size (2000, 3). How can I make plot understand that each line of the set points must be painted with the corresponding line in the colour array ? Matthieu 
From: John Hunter <jdh2358@gm...>  20070309 14:18:48

On 3/9/07, Fernando Perez <fperez.net@...> wrote: > (or matlab for that matter) in my life, I was rather surprised by the > behavior and (mis)understood it as a bug. > > I've always gotten by just fine in pylab without even knowing what > hold did, and simply clearing the figure by hand when needed or just > making a new one. Just to add a few data points  the default "hold" state can be set in your rc file. It is a property of the current figure and the current axes. In you example, when you set fold before creating the third figure, the setting applued to the current figure (figure 2) but not the next figure. JDH 
From: John Hunter <jdh2358@gm...>  20070309 14:16:19

On 3/9/07, Uwe Schmitt <uschmitt@...> wrote: > I would like to display an image using pylab > without automatic scaling to the default size of the plot window. > > How can I achieve this ? If you want displayed image to just be a pixel dump of the actual image use figimage http://matplotlib.sf.net/examples/figimage_demo.py JDH 
From: John Hunter <jdh2358@gm...>  20070309 14:10:27

On 3/9/07, Matthieu Brucher <matthieu.brucher@...> wrote: > Hi, > > I'm trying to plot a set of points, each point having a different color. > For the moment, I'm trying to do something like that : > > for indice in range(0, points.shape[0]): > pl.plot(points[indice, 0], points[indice, 1], 'o', c = > colours[indice,:], hold = True) > > where points is a numpy array of point and colours is a numpy array of > dimension (points.shape[0], 3) > > With Matlab, something like this would function, but not in matplotlib, it > tells me : > ValueError: need more than 0 values to unpack Complete examples always help ince we have no way of knowing what the points data structures look like, but I'll hazard a gues. The x and y arguments to "plot" need to be sequences. Ie, something like plot([0.5], [0.5], 'ro') It can be inefficient to plot many separate points this way  if you have a lot of points, use a matplotlib.collections.RegularPolyCollection or scatter. JDH 
From: Ken McIvor <mcivor@ii...>  20070309 13:08:28

On Mar 9, 2007, at 5:11 AM, Uwe Schmitt wrote: > > Thanks, but I can not access this article from the mailing lists > archive. > On sourceforge the newest posting is from 23th feb. I'm not sure what the problem with SourceForge is. I'll forward you that email offlist. Ken 
From: Zack 24 <zack24@gm...>  20070309 11:26:55

Hi, All Is it possible to draw any graphical primitives in the plot area using its scale? Let say, I want to plot a filled circle there. Where do I have to look on? Thanks in advance, Alexey 
From: Uwe Schmitt <uschmitt@mi...>  20070309 11:11:23

Ken McIvor wrote: > Uwe, > > I don't know the answer to your question, but yesterday Rob Hetland > sent out and email entitled "Creating a nonlinear colormap." that > includes example code. That might help you get started. > > Ken > Thanks, but I can not access this article from the mailing lists archive. On sourceforge the newest posting is from 23th feb. Greetings, Uwe 
From: Matthieu Brucher <matthieu.brucher@gm...>  20070309 09:35:08

Hi, I'm trying to plot a set of points, each point having a different color. For the moment, I'm trying to do something like that : for indice in range(0, points.shape[0]): pl.plot(points[indice, 0], points[indice, 1], 'o', c = colours[indice,:], hold = True) where points is a numpy array of point and colours is a numpy array of dimension (points.shape[0], 3) With Matlab, something like this would function, but not in matplotlib, it tells me : ValueError: need more than 0 values to unpack I am missing something ? Matthieu 
From: Uwe Schmitt <uschmitt@mi...>  20070309 09:19:09

Hello, I would like to display an image using pylab without automatic scaling to the default size of the plot window. How can I achieve this ? Greetings, Uwe 
From: Fernando Perez <fperez.net@gm...>  20070309 07:36:11

Hi Simon, On 3/8/07, Simon Wood <sgwoodjr@...> wrote: > On 3/8/07, Fernando Perez <fperez.net@...> wrote: > > Hi all, > > > > today at work we ran into some odd behavior, all of which seems to be > > triggered by calling hold(). I'm using a fresh SVN build from this > > afternoon. > > > > Here's the first example demonstrating the problem, it's best to run > > this in a fresh pylab shell or from the command line, since I suspect > > internal state matters (when it shouldn't): > > > > import pylab as P > > > > x = P.arange(10) > > y = x+1 > > > > P.figure() > > P.plot(x,label='one') > > P.plot(y,label='two') > > P.legend() > > P.title('Two plots ok') > > > > P.figure() > > P.hold(True) > > P.plot(x,label='one') > > P.plot(y,label='two') > > P.legend() > > P.title('Two plots ok  HOLD called') > > P.hold(False) > > > > P.figure() > > P.plot(x,label='one') > > P.plot(y,label='two') > > P.legend() > > P.title('One plot MISSING!') > > > > P.show() > > > > #### EOF > > > > I do not think this is a bug. The default value for the hold function is > True. When you originally plotted x and y the hold state was already set to > True. So, actually your first case and second case are the same. However, > right before your third figure you set P.hold(False) . You then plot x > followed by y. So, yes I would expect to see only one line in the final > figure. This is exactly like Matlab (perhaps with the exception that the > default state of hold is False in Matlab). Perhaps that is what is confusing > you and your colleague. In Matlab the default state of hold is False, > however in Matplotlib is looks like the default state of hold is True. Many thanks for your clear explanation. Since I had never used hold (or matlab for that matter) in my life, I was rather surprised by the behavior and (mis)understood it as a bug. I've always gotten by just fine in pylab without even knowing what hold did, and simply clearing the figure by hand when needed or just making a new one. Sorry for the noise. Regards, f 
From: Simon Wood <sgwoodjr@gm...>  20070309 04:00:22

On 3/8/07, Fernando Perez <fperez.net@...> wrote: > > Hi all, > > today at work we ran into some odd behavior, all of which seems to be > triggered by calling hold(). I'm using a fresh SVN build from this > afternoon. > > Here's the first example demonstrating the problem, it's best to run > this in a fresh pylab shell or from the command line, since I suspect > internal state matters (when it shouldn't): > > import pylab as P > > x = P.arange(10) > y = x+1 > > P.figure() > P.plot(x,label='one') > P.plot(y,label='two') > P.legend() > P.title('Two plots ok') > > P.figure() > P.hold(True) > P.plot(x,label='one') > P.plot(y,label='two') > P.legend() > P.title('Two plots ok  HOLD called') > P.hold(False) > > P.figure() > P.plot(x,label='one') > P.plot(y,label='two') > P.legend() > P.title('One plot MISSING!') > > P.show() > > #### EOF > I do not think this is a bug. The default value for the hold function is True. When you originally plotted x and y the hold state was already set to True. So, actually your first case and second case are the same. However, right before your third figure you set P.hold(False) . You then plot x followed by y. So, yes I would expect to see only one line in the final figure. This is exactly like Matlab (perhaps with the exception that the default state of hold is False in Matlab). Perhaps that is what is confusing you and your colleague. In Matlab the default state of hold is False, however in Matplotlib is looks like the default state of hold is True. Simon 
From: Fernando Perez <fperez.net@gm...>  20070309 02:57:49

Hi all, today at work we ran into some odd behavior, all of which seems to be triggered by calling hold(). I'm using a fresh SVN build from this afternoon. Here's the first example demonstrating the problem, it's best to run this in a fresh pylab shell or from the command line, since I suspect internal state matters (when it shouldn't): import pylab as P x = P.arange(10) y = x+1 P.figure() P.plot(x,label='one') P.plot(y,label='two') P.legend() P.title('Two plots ok') P.figure() P.hold(True) P.plot(x,label='one') P.plot(y,label='two') P.legend() P.title('Two plots ok  HOLD called') P.hold(False) P.figure() P.plot(x,label='one') P.plot(y,label='two') P.legend() P.title('One plot MISSING!') P.show() #### EOF And here's the second manifestation of the problem, where the colorbar gets all messed up: import numpy as N import pylab as P a = N.random.rand(64,64) P.figure() P.imshow(a) P.colorbar() P.title('Colorbar OK') # If the hold() calls are commented out, the problem disappears P.figure() P.hold(True) P.plot(range(10)) P.hold(False) P.figure() P.imshow(a) P.colorbar() P.title('Colorbar BROKEN!') P.show() #### EOF It looks like making calls to hold() messes up internal state in pylab somehow. I've never used hold() myself before, but my officemate did, coming from matlab, and started seeing bizarre behavior. These are little selfcontained examples showing the problem. Cheers, f 