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) 

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) 
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) 
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) 
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) 
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) 
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) 
2012 
_{Jan}
(322) 
_{Feb}
(414) 
_{Mar}
(377) 
_{Apr}
(179) 
_{May}
(173) 
_{Jun}
(234) 
_{Jul}
(151) 
_{Aug}

_{Sep}

_{Oct}

_{Nov}

_{Dec}

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) 
S  M  T  W  T  F  S 






1
(10) 
2
(3) 
3
(5) 
4
(7) 
5
(18) 
6
(4) 
7
(15) 
8
(7) 
9
(10) 
10
(4) 
11
(18) 
12
(15) 
13
(11) 
14
(11) 
15
(4) 
16
(28) 
17
(17) 
18
(22) 
19
(12) 
20
(19) 
21
(17) 
22
(14) 
23
(4) 
24
(3) 
25
(6) 
26
(8) 
27
(13) 
28
(11) 
29
(21) 
30
(3) 
31
(5) 






From: Simson L. Garfinkel's Treo 700p <simsong@ac...>  20061216 21:30:20

Yep. I would like to pass in a list of lists, where each sublist (or array) describes a boxplot to plot. Meanwhile, i've been having fun with histograms. The Y axis labels are a pain. I think defaulting to scientific notation, as matplotlib frequently does, is annoying... ___ Sent with SnapperMail http://www.snappermail.com ...... Original Message ....... On Sat, 16 Dec 2006 11:02:28 1000 "Eric Firing" <efiring@...> wrote: >Pierre GM wrote: >>> And for the work I'm doing, I have a >>> different number of observations and data points on different days, >>> so it's a pain that the current boxplot infrastructure expects all of >>> the boxes to be in a single array. Hence my questions. >> >> Ah OK, now I get it. Sorry for being a bit slow today. >> So yes, there's a problem here. The sequence is transformed into an array >> with 'asarray', which obviously won't work if you have different sizes of >> dataset. >> >> But there's a trick, tested on numpy: >> >> import numpy >> set1 = (rand(50)+1) * 100 >> set2 = (rand(25)+2) * 100 >> data = array([set1,set2], dtype=numpy.object_) >> boxplot(data,positions=[732659.,732660.]) >> >> The trick here is to force the data as objects, and not as floats. Your array >> is in fact an array of arrays of different sizes. That's enough to fool >> asarray. > >It sounds like the real problem is that the initial use of asarray in >boxplot is a bugit should transparently support an object array, as >you suggest (but numpy only), or an ordinary array, *or* a list or tuple >of data vectors, and all this should be clear in the docstring and the >example. Correct? I hope so, because I have made the change in svn. >(Well, maybe not enough changes to the example yet.) > >Eric > 
From: Pierre GM <pgmdevlist@gm...>  20061216 21:23:27

On Saturday 16 December 2006 16:02, Eric Firing wrote: > It sounds like the real problem is that the initial use of asarray in > boxplot is a bugit should transparently support an object array, as > you suggest (but numpy only), or an ordinary array, *or* a list or tuple > of data vectors, and all this should be clear in the docstring and the > example. Correct? I hope so, because I have made the change in svn. > (Well, maybe not enough changes to the example yet.) Fully agreed. There's no need for the transformation to array: the only variable which is arrayrelated is the number of columns (viz, the number of boxes to plot). OK, there's also that: for i,pos in enumerate(positions): d = x[:,i] But it'd be as easy to enumerate the array (after a first transpose, if its a regular ndarray...) 
From: Eric Firing <efiring@ha...>  20061216 21:02:42

Pierre GM wrote: >> And for the work I'm doing, I have a >> different number of observations and data points on different days, >> so it's a pain that the current boxplot infrastructure expects all of >> the boxes to be in a single array. Hence my questions. > > Ah OK, now I get it. Sorry for being a bit slow today. > So yes, there's a problem here. The sequence is transformed into an array > with 'asarray', which obviously won't work if you have different sizes of > dataset. > > But there's a trick, tested on numpy: > > import numpy > set1 = (rand(50)+1) * 100 > set2 = (rand(25)+2) * 100 > data = array([set1,set2], dtype=numpy.object_) > boxplot(data,positions=[732659.,732660.]) > > The trick here is to force the data as objects, and not as floats. Your array > is in fact an array of arrays of different sizes. That's enough to fool > asarray. It sounds like the real problem is that the initial use of asarray in boxplot is a bugit should transparently support an object array, as you suggest (but numpy only), or an ordinary array, *or* a list or tuple of data vectors, and all this should be clear in the docstring and the example. Correct? I hope so, because I have made the change in svn. (Well, maybe not enough changes to the example yet.) Eric 
From: Pierre GM <pgmdevlist@gm...>  20061216 19:45:41

Sergio, I think the line you see comes from plotting two shape on top one another. You may want to redefine your polygon: the easier would be something like: tt = concatenate((t,t[::1])) vtx = concatenate((s3,s2[::1])) fill(tt, vtx, '#e9ccce', linewidth=0) With the first command, you build a series of x coordinates from 0 to 1.01 and back to 0 (that's the t[::1]) with second, you build the y ccordinates sequence, by taking the corresponindg point of s3, and then from s2 in reverse order. Now, your polygon is fully defined. 
From: Sergio Drumond Ventura <ventura@uf...>  20061216 19:20:47

Hi, I am a new user of matplotlib. First of all I would like to say that the people working on matplotlib is doing a great job. Well, I have tried to use the 'fill', but I cannot get rid of the lines. I have tried to use 'linewidth=0' at the end, but it did not work. Could somebody, please, tell me if I am doing something wrong ? Thank you. Sergio.  #!/usr/bin/env python from pylab import * from matplotlib.patches import Polygon t = arange(0.0, 1.0+0.01, 0.01) s1 = t s2 = t*t s3 = t*t*t text(0.50, 0.4, r"$d(f_2,f_3)$", horizontalalignment='center', color= '#8f0100', fontsize=30) xticks(size=20) yticks(size=20) fill(t, s3, '#e9ccce', linewidth=0) fill(t, s2, 'w', linewidth=0) savefig('diamxn2.eps') 
From: Sergio Drumond Ventura <damxtha@gm...>  20061216 19:18:13

Hi, I am a new user of matplotlib. First of all I would like to say that the people working on matplotlib is doing a great job. Well, I have tried to use the 'fill', but I cannot get rid of the lines. I have tried to use 'linewidth=0' at the end, but it did not work. Could somebody, please, tell me if I am doing something wrong ? Thank you. Sergio.  #!/usr/bin/env python from pylab import * from matplotlib.patches import Polygon t = arange(0.0, 1.0+0.01, 0.01) s1 = t s2 = t*t s3 = t*t*t text(0.50, 0.4, r"$d(f_2,f_3)$", horizontalalignment='center', color= '#8f0100', fontsize=30) xticks(size=20) yticks(size=20) fill(t, s3, '#e9ccce', linewidth=0) fill(t, s2, 'w', linewidth=0) savefig('diamxn2.eps') 
From: Pierre GM <pgmdevlist@gm...>  20061216 18:58:38

On Saturday 16 December 2006 13:47, Simson Garfinkel wrote: > > I apologize if I offended anyone, this was really not my intention > > at all. > > Oh, I was never offended. Thanks a lot for your patience nevertheless. > I think that it's possible to get impressive results in a few hours, > but not become a pro. I see that as an advantage: you can never get bored, there's always something new to learn (I should have listened to my mom and spend less time in front of the TV as a kid). But I admit it can get a bit frustrating, when you eventually find out that there was a really simple solution to a problem, alas undocumented and buried in the code (for example, the xaxis_date thingie which doesn't do much). > I've been using matplotlib for something like > 2040 hours right now. I've done some neat things, but have had some > problems. That's when the mailing list becomes really useful. > I've also written a neat preprocessor that allows you to embed > python and matplotlib code in LaTeX, so you don't need to have it all > spread out. And you can populate the results from SQL queries, right > there in the LaTeX. It makes paper writing much easier. Oh, that sounds great ! Could you post it somewhere ? I'm sure it'd be quite useful (I do have a need for it myself...) 
From: Simson Garfinkel <simsong@ac...>  20061216 18:47:24

> > I apologize if I offended anyone, this was really not my intention > at all. Oh, I was never offended. > My > point was that after only a few hours, it is indeed possible to get > impressive results and become a real MPL pro. I think that it's possible to get impressive results in a few hours, but not become a pro. I've been using matplotlib for something like 2040 hours right now. I've done some neat things, but have had some problems. I've also written a neat preprocessor that allows you to embed python and matplotlib code in LaTeX, so you don't need to have it all spread out. And you can populate the results from SQL queries, right there in the LaTeX. It makes paper writing much easier. 
From: Pierre GM <pgmdevlist@gm...>  20061216 18:43:14

On Saturday 16 December 2006 13:01, David Chin wrote: > On 12/16/06, Simson Garfinkel <simsong@...> wrote: > > Thanks. I have roughly 30 years of programming experience and know > > something like 20+ languages. The learning curve here is steep, and I > > think that a lot could be done to make it less steep. > > I agree. Pierre, maybe you should google Simson's name here > before taking a condescending tone. I apologize if I offended anyone, this was really not my intention at all. My point was that after only a few hours, it is indeed possible to get impressive results and become a real MPL pro. > Anyway, I agree with the other suggestion that a lot of the stuff here > should be wikied. Now, Pierre said that one can edit the wiki, but when > I tried it ( http://scipy.org/Cookbook/Matplotlib?action=edit ), I get an > error saying "You are not allowed to edit this page." So, may I suggest > that the Wiki be opened up for editing? Information flows much more > quickly if everyone can contribute. Well, I think you have to register before being able to edit pages. There's a login button on the top right of your screen. But I agree that it's not intuitive (I have to poke around for a while to find it) (and then remember my login name). 
From: Xavier Gnata <gnata@ob...>  20061216 18:42:54

Hi, Each time I'm working on C++ codes using vector or valarray, I would like to be able to plot them. The problem is that there is no straitforward way to do that in C++. My goal is not to code a QT or GTK application but only to be able to plot 1D and 2D things from one given large C++ code without having to add lots of lines of codes in my code (let say it is intend to be used in debug phase). Questions : Is there a way to call pylab plot and imshow from a C++ code ? In this case, I do not care if we have to copy the array and it can be sl= ow. It would be a so nice feature to debug C++ image processing codes. Any example of code is welcome even they are not calling matplotlib but anthing else in python. Xavier. ps : In my codes, 2D images are stored as in a class derived from valarray (1D array) adding the size of the image along the 2 directions as private members. =20 ############################################ Xavier Gnata CRAL  Observatoire de Lyon 9, avenue Charles Andr=E9 69561 Saint Genis Laval cedex Phone: +33 4 78 86 85 28 Fax: +33 4 78 86 83 86 Email: gnata@... ############################################=20 
From: Pierre GM <pgmdevlist@gm...>  20061216 18:30:42

> And for the work I'm doing, I have a > different number of observations and data points on different days, > so it's a pain that the current boxplot infrastructure expects all of > the boxes to be in a single array. Hence my questions. Ah OK, now I get it. Sorry for being a bit slow today. So yes, there's a problem here. The sequence is transformed into an array with 'asarray', which obviously won't work if you have different sizes of dataset. But there's a trick, tested on numpy: import numpy set1 = (rand(50)+1) * 100 set2 = (rand(25)+2) * 100 data = array([set1,set2], dtype=numpy.object_) boxplot(data,positions=[732659.,732660.]) The trick here is to force the data as objects, and not as floats. Your array is in fact an array of arrays of different sizes. That's enough to fool asarray. 
From: Simson Garfinkel <simsong@ac...>  20061216 18:10:18

On Dec 16, 2006, at 1:01 PM, Pierre GM wrote: >> Hi, Pierre. There's a lot of assumptions here. > Indeed, and I apologize > >> I sort of know what numarray, Numeric and numpy are, but I don't care >> all that much. I'm just interested in matplotlib for the plotting. > Well, matplotlib relies on some packages to handle data arrays. > It's probably > a good idea to check what you have below the hood, just in case > something > goes wrong. It'll make things easier to help you. Thanks. In fact, after I read through the matplotlib tutorial and user's manual, I downloaded and read the numpy manual too. It's a nice package. I especially liked the line about numpy not making things possible that weren't possible before, but that it just allows things to be finished before we are dead. Overall, the package is really impressive. I don't like the way that arrays aren't resizable, though. And for the work I'm doing, I have a different number of observations and data points on different days, so it's a pain that the current boxplot infrastructure expects all of the boxes to be in a single array. Hence my questions. > >> The point of my email (and the questions below) is that the entire >> scipy.org website is written for people who already know what's going >> on. If you want to expand the user community (and simultaneously cut >> down on questions) you need to make things dramatically more >> understandable than they currently are. > > That's true, and I guess that's the reason why there's a wiki. > Please feel > free to add your comments and suggestions. Thanks. I will. > >> A related problem is the MoinMoin wiki. It is not a widely used wiki >> and it has many usability problems. It is dramatically harder to use >> than, say, mediawiki. > > But it happens to be the solution that has been chosen. Yep. > 
From: Pierre GM <pgmdevlist@gm...>  20061216 18:06:38

> I want multiple boxes on a single plot, with one box per day. Take a > look at how I've done it with just plot() and some error bars... I'm still not sure I understand where the problem is: You want several boxes in a plot ? Something along the lines of what I already sent you ? > boxplot([set1, set2],positions=[732659,732660]) Then once again, just construct of sequences of sets, a sequence of dates (as ordinals), and use something like: boxplot(setsequence, positions=datesequence). Alternatively, follow the boxplot_demo example. Then, you'll have to use the trick I sent earlier gca().set_xticklabels([num2date(x).strftime(fmt) for x in gca().get_xticklabels()]) 
From: David Chin <david.chin@gm...>  20061216 18:01:23

On 12/16/06, Simson Garfinkel <simsong@...> wrote: > > On Dec 16, 2006, at 12:02 PM, Pierre GM wrote: > > I know, the learning curve is a bit steep at first, but soon you'll > > be a real > > pro. > > Thanks. I have roughly 30 years of programming experience and know > something like 20+ languages. The learning curve here is steep, and I > think that a lot could be done to make it less steep. I agree. Pierre, maybe you should google Simson's name here before taking a condescending tone. Anyway, I agree with the other suggestion that a lot of the stuff here should be wikied. Now, Pierre said that one can edit the wiki, but when I tried it ( http://scipy.org/Cookbook/Matplotlib?action=edit ), I get an error saying "You are not allowed to edit this page." So, may I suggest that the Wiki be opened up for editing? Information flows much more quickly if everyone can contribute. Cheers, Dave 
From: Pierre GM <pgmdevlist@gm...>  20061216 18:01:21

> Hi, Pierre. There's a lot of assumptions here. Indeed, and I apologize > I sort of know what numarray, Numeric and numpy are, but I don't care > all that much. I'm just interested in matplotlib for the plotting. Well, matplotlib relies on some packages to handle data arrays. It's probably a good idea to check what you have below the hood, just in case something goes wrong. It'll make things easier to help you. > The point of my email (and the questions below) is that the entire > scipy.org website is written for people who already know what's going > on. If you want to expand the user community (and simultaneously cut > down on questions) you need to make things dramatically more > understandable than they currently are. That's true, and I guess that's the reason why there's a wiki. Please feel free to add your comments and suggestions. > A related problem is the MoinMoin wiki. It is not a widely used wiki > and it has many usability problems. It is dramatically harder to use > than, say, mediawiki. But it happens to be the solution that has been chosen. 
From: Simson Garfinkel <simsong@ac...>  20061216 17:54:38

I agree. It may be common in matlab, but it really doesn't belong in python. On Dec 16, 2006, at 12:50 PM, Eric Firing wrote: > >>> BTW, this whole subplot(ijk) instead of subplot(i,j,k) notation is >>> really, really confusing to me... >> Don't get overwhelmed. ijk is a shortcut for (i, j, k), that works >> well if you're working with less than 10 plots in either direction. > > It is a holdover from the early days of Matlab. It makes mpl more > Matlablike (for better or worse) and saves 24 keystrokes. > Personally, I don't like it and would be inclined to discourage it > in mpl. > > Eric > 
From: Eric Firing <efiring@ha...>  20061216 17:50:18

>> BTW, this whole subplot(ijk) instead of subplot(i,j,k) notation is >> really, really confusing to me... > > Don't get overwhelmed. ijk is a shortcut for (i, j, k), that works well if > you're working with less than 10 plots in either direction. It is a holdover from the early days of Matlab. It makes mpl more Matlablike (for better or worse) and saves 24 keystrokes. Personally, I don't like it and would be inclined to discourage it in mpl. Eric 
From: Simson Garfinkel <simsong@ac...>  20061216 17:41:20

On Dec 16, 2006, at 12:02 PM, Pierre GM wrote: > >> I'd love to speak python to it. But it's harder when all of the >> examples are in matlab... > > :) > Well, please have a look to pythonic_matplotlib.py in your examples > folder. > >>> fig = figure() >>> ax1 = fig.add_subplot(121) >>> ax2=fig.add_subplot(122) >> >> Hm. I'll need to figure out why these two subplots appear on the same >> axis. > > What do you mean ? You want two plots on a figure, or two figures? > You want one plot in the topleft corner, one in hte bottom right ? > You can do > that as well, just tell matplotlib where to plot the axes (a bit of > terminology here: an axes is a box in your figure, in which you > will draw a > subplot). I want multiple boxes on a single plot, with one box per day. Take a look at how I've done it with just plot() and some error bars... 
From: Simson Garfinkel <simsong@ac...>  20061216 17:39:01

On Dec 16, 2006, at 11:58 AM, Pierre GM wrote: >> I'm very confused by the wiki in general. I click on "wiki" and it >> takes me >> to something that doesn't obviously have anything to do with >> matplotlib... > > Well, it does say: matplotlib cookbook. > >> Like, what's scipy.org? Is it a company? Who is EnThought? > Oh. > What are you using to manipulate arrays ? numarray, Numeric, or > numpy ? > Assuming that you use numpy, then you must know what scipy is, > right ? If > not, well, br > scipy.org is just a central site for numpy/scipyrelated information. > Enthought is a private company that works extensively with Python > and numpy > in particular, and that hosts the site. Hi, Pierre. There's a lot of assumptions here. I do most of my own manipulations in SQL and with customwritten programs in C, C++, and Python. I sort of know what numarray, Numeric and numpy are, but I don't care all that much. I'm just interested in matplotlib for the plotting. The point of my email (and the questions below) is that the entire scipy.org website is written for people who already know what's going on. If you want to expand the user community (and simultaneously cut down on questions) you need to make things dramatically more understandable than they currently are. A related problem is the MoinMoin wiki. It is not a widely used wiki and it has many usability problems. It is dramatically harder to use than, say, mediawiki. > >> Amy I allowed to contribute to the wiki? It doesn't look like it. >> The whole >> thing is not very friendly. > > It's a wiki, so yes, you can contribute. No, it's not especially > friendly, in > the sense that nobody's here to hold your hand. > >> And what is this whole MoinMoin thing? > "MoinMoin is a Python WikiClone, based on PikiPiki. " > This converstaion is really becoming surrealistic. > 
From: Pierre GM <pgmdevlist@gm...>  20061216 17:04:14

> I'd love to speak python to it. But it's harder when all of the > examples are in matlab... :) Well, please have a look to pythonic_matplotlib.py in your examples folder. > > fig = figure() > > ax1 = fig.add_subplot(121) > > ax2=fig.add_subplot(122) > > Hm. I'll need to figure out why these two subplots appear on the same > axis. What do you mean ? You want two plots on a figure, or two figures? You want one plot in the topleft corner, one in hte bottom right ? You can do that as well, just tell matplotlib where to plot the axes (a bit of terminology here: an axes is a box in your figure, in which you will draw a subplot). > BTW, this whole subplot(ijk) instead of subplot(i,j,k) notation is > really, really confusing to me... Don't get overwhelmed. ijk is a shortcut for (i, j, k), that works well if you're working with less than 10 plots in either direction. I know, the learning curve is a bit steep at first, but soon you'll be a real pro. 
From: Pierre GM <pgmdevlist@gm...>  20061216 16:58:22

> I'm very confused by the wiki in general. I click on "wiki" and it takes me > to something that doesn't obviously have anything to do with matplotlib... Well, it does say: matplotlib cookbook. > Like, what's scipy.org? Is it a company? Who is EnThought? Oh. What are you using to manipulate arrays ? numarray, Numeric, or numpy ? Assuming that you use numpy, then you must know what scipy is, right ? If not, well, br scipy.org is just a central site for numpy/scipyrelated information. Enthought is a private company that works extensively with Python and numpy in particular, and that hosts the site. > Amy I allowed to contribute to the wiki? It doesn't look like it. The whole > thing is not very friendly. It's a wiki, so yes, you can contribute. No, it's not especially friendly, in the sense that nobody's here to hold your hand. > And what is this whole MoinMoin thing? "MoinMoin is a Python WikiClone, based on PikiPiki. " This converstaion is really becoming surrealistic. 
From: Simson Garfinkel <simsong@ac...>  20061216 16:48:51

> > >> Now, how do I get two boxplots on the same plot? > > Well, just draw two axes. > Simson, now that you're more experienced with matplotlib, you > should really > start speaking python to it. I'd love to speak python to it. But it's harder when all of the examples are in matlab... > > fig = figure() > ax1 = fig.add_subplot(121) > ax2=fig.add_subplot(122) Hm. I'll need to figure out why these two subplots appear on the same axis. BTW, this whole subplot(ijk) instead of subplot(i,j,k) notation is really, really confusing to me... > > ax1.boxplot([set1, set2],positions=[732659,732660]) > ax2.boxplot([set2, set1],positions=[732659,732660]) > ax1.set_xticklabels([num2date(x).strftime(timefmt) for x in > ax1.get_xticks()]) > ax2.set_xticklabels([num2date(x).strftime(timefmt) for x in > ax2.get_xticks()]) > > 
From: Pierre GM <pgmdevlist@gm...>  20061216 16:44:42

On Friday 15 December 2006 21:07, Simson Garfinkel wrote: > Hm. thanks for the info. But it's not perfect... I get times in my > formats, but not the dates. Here is the sample code: Yeah, I agree, the situation is far from ideal. Besides, it turns out that there's no deep magic behind have_dates, which is just a way to tell the axis to use AutoDateFormatter. Which we don't need. So: Plot your boxeds with the positions flag: > boxplot([set1, set2],positions=[732659,732660]) > ax = gca() Then use num2date: timefmt = '%b%d%Y' gca().set_xticklabels([num2date(x).strftime(timefmt) for x in gca().get_xticks()]) > Now, how do I get two boxplots on the same plot? Well, just draw two axes. Simson, now that you're more experienced with matplotlib, you should really start speaking python to it. fig = figure() ax1 = fig.add_subplot(121) ax2=fig.add_subplot(122) ax1.boxplot([set1, set2],positions=[732659,732660]) ax2.boxplot([set2, set1],positions=[732659,732660]) ax1.set_xticklabels([num2date(x).strftime(timefmt) for x in ax1.get_xticks()]) ax2.set_xticklabels([num2date(x).strftime(timefmt) for x in ax2.get_xticks()]) 
From: Simson Garfinkel <simsong@ac...>  20061216 16:42:28

It would be useful if grid had two options: drawHorizontalLines = True drawVerticalLines = True This way, people who look for suppressing the X or Y lines would find it in the logical location. 
From: Simson L. Garfinkel <simsong@ac...>  20061216 16:29:16

 Original Message  From: "Angus McMorland" <amcmorl@...> > We really shoud wiki more of these email discussions as they come > along. It's so much easier to search there, since things are in some > sort of logical arrangement. I agree. I'm very confused by the wiki in general. I click on "wiki" and it takes me to something that doesn't obviously have anything to do with matplotlib... Like, what's scipy.org? Is it a company? Who is EnThought? Amy I allowed to contribute to the wiki? It doesn't look like it. The whole thing is not very friendly. And what is this whole MoinMoin thing? 