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
(295) |
Aug
(239) |
Sep
(276) |
Oct
(355) |
Nov
(144) |
Dec
(108) |
2013 |
Jan
(170) |
Feb
(89) |
Mar
(204) |
Apr
(133) |
May
(142) |
Jun
(89) |
Jul
(160) |
Aug
(180) |
Sep
(69) |
Oct
(136) |
Nov
(83) |
Dec
(32) |
2014 |
Jan
(71) |
Feb
(90) |
Mar
(161) |
Apr
(117) |
May
(78) |
Jun
(94) |
Jul
(60) |
Aug
(83) |
Sep
(102) |
Oct
(132) |
Nov
(154) |
Dec
(96) |
2015 |
Jan
(45) |
Feb
(138) |
Mar
(176) |
Apr
(132) |
May
(119) |
Jun
(124) |
Jul
(77) |
Aug
(31) |
Sep
(34) |
Oct
(22) |
Nov
(23) |
Dec
(9) |
2016 |
Jan
(26) |
Feb
(17) |
Mar
(10) |
Apr
(8) |
May
(4) |
Jun
(8) |
Jul
(6) |
Aug
(5) |
Sep
(9) |
Oct
(4) |
Nov
|
Dec
|
2017 |
Jan
(5) |
Feb
(7) |
Mar
(1) |
Apr
(5) |
May
|
Jun
(3) |
Jul
(6) |
Aug
(1) |
Sep
|
Oct
(2) |
Nov
(1) |
Dec
|
2018 |
Jan
|
Feb
|
Mar
|
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2020 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
2025 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
S | M | T | W | T | F | S |
---|---|---|---|---|---|---|
|
1
(13) |
2
(12) |
3
(3) |
4
(13) |
5
(13) |
6
(2) |
7
(5) |
8
(17) |
9
(9) |
10
(10) |
11
(16) |
12
(8) |
13
(10) |
14
(1) |
15
(5) |
16
(5) |
17
(7) |
18
(13) |
19
(9) |
20
|
21
|
22
(2) |
23
(3) |
24
(5) |
25
(5) |
26
(14) |
27
(1) |
28
(2) |
29
(18) |
30
(5) |
31
(22) |
|
|
|
Dear all, is there the possiblity in matplolib to buind dendograms ? I've searched a bit bout found no examples of it it seems not implemented is there a plan for doing it ? Thanks in advance for all reply Giorgio
Sorry I didn't know the difference... N. Le Friday 19 October 2007 10:52:25 Darren Dale, vous avez =E9crit=A0: > On Friday 19 October 2007 10:38:36 am hu...@ya... wrote: > > Le Friday 19 October 2007 08:37:00 Darren Dale, vous avez =E9crit=A0: > > > On Thursday 18 October 2007 11:49:50 am hu...@ya... wrote: > > > > Hi, > > > > > > > > I have a small problem with label. > > > > > > > > > > > > plot([0,1],[0,1]) > > > > xlabel(r'$ABCDEF$',fontsize=3D35) > > > > > > > > (but the size doesn't change anything) I obtain the result visible = on > > > > the figure join. I think there are a problem when using latex and h= ow > > > > the first character is handle. > > > > > > I don't think its a problem with matplotlib; I can't reproduce the > > > problem on my machine. Maybe its an issue with your dvipng? I'm using > > > version 1.9. > > > > Oups I found the problem, I don't know why because it was working fine > > before the upgrade to gutsy but I have to change matplotlib configurati= on > > and everything is working fine if I put in the file: > > > > rc('text', usetex=3DTrue) > > In your first email you said you were using latex, but you were actually > using mathtext. I can confirm the problem when I disable usetex and inste= ad > use mathtext. Mike, is this something easy to fix? > > Darren
On Friday 19 October 2007 10:38:36 am hu...@ya... wrote: > Le Friday 19 October 2007 08:37:00 Darren Dale, vous avez =E9crit=A0: > > On Thursday 18 October 2007 11:49:50 am hu...@ya... wrote: > > > Hi, > > > > > > I have a small problem with label. > > > > > > > > > plot([0,1],[0,1]) > > > xlabel(r'$ABCDEF$',fontsize=3D35) > > > > > > (but the size doesn't change anything) I obtain the result visible on > > > the figure join. I think there are a problem when using latex and how > > > the first character is handle. > > > > I don't think its a problem with matplotlib; I can't reproduce the > > problem on my machine. Maybe its an issue with your dvipng? I'm using > > version 1.9. > > > Oups I found the problem, I don't know why because it was working fine > before the upgrade to gutsy but I have to change matplotlib configuration > and everything is working fine if I put in the file: > > rc('text', usetex=3DTrue) In your first email you said you were using latex, but you were actually us= ing=20 mathtext. I can confirm the problem when I disable usetex and instead use=20 mathtext. Mike, is this something easy to fix? Darren
Oups I found the problem, I don't know why because it was working fine befo= re=20 the upgrade to gutsy but I have to change matplotlib configuration and=20 everything is working fine if I put in the file: rc('text', usetex=3DTrue) sorry to have bother you with this, N. Le Friday 19 October 2007 08:37:00 Darren Dale, vous avez =E9crit=A0: > On Thursday 18 October 2007 11:49:50 am hu...@ya... wrote: > > Hi, > > > > I have a small problem with label. > > > > > > plot([0,1],[0,1]) > > xlabel(r'$ABCDEF$',fontsize=3D35) > > > > (but the size doesn't change anything) I obtain the result visible on t= he > > figure join. I think there are a problem when using latex and how the > > first character is handle. > > I don't think its a problem with matplotlib; I can't reproduce the problem > on my machine. Maybe its an issue with your dvipng? I'm using version 1.9. > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Matplotlib-users mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-users
I don't think the problem is in dvipng because I have exactly the same when= =20 I'm using GtkAgg and before your message I didn't have dvipng installed. I'= m=20 using ubuntu gutsy so perhaps there are a change in the lib. N.=20 Le Friday 19 October 2007 08:37:00 Darren Dale, vous avez =E9crit=A0: > On Thursday 18 October 2007 11:49:50 am hu...@ya... wrote: > > Hi, > > > > I have a small problem with label. > > > > > > plot([0,1],[0,1]) > > xlabel(r'$ABCDEF$',fontsize=3D35) > > > > (but the size doesn't change anything) I obtain the result visible on t= he > > figure join. I think there are a problem when using latex and how the > > first character is handle. > > I don't think its a problem with matplotlib; I can't reproduce the problem > on my machine. Maybe its an issue with your dvipng? I'm using version 1.9. > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > _______________________________________________ > Matplotlib-users mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-users
On Thursday 18 October 2007 11:49:50 am hu...@ya... wrote: > Hi, > > I have a small problem with label. > > > plot([0,1],[0,1]) > xlabel(r'$ABCDEF$',fontsize=35) > > (but the size doesn't change anything) I obtain the result visible on the > figure join. I think there are a problem when using latex and how the first > character is handle. I don't think its a problem with matplotlib; I can't reproduce the problem on my machine. Maybe its an issue with your dvipng? I'm using version 1.9.
Hey, Ive got 10 strings of data that i plot into 1 big window, but somehow matplotlib gives me a very strange set-up. I am rather new to matplotlib and python so im kinda stuck now! heres an image of what i get and part of my code: http://www.nabble.com/file/p13290670/Bildschirmphoto1.png ############################################### from scipy import * import pylab from scipy.optimize import leastsq import sys #Functions def pload(filename): """function for loading special Mira data""" def residuals(p, y, x): A,k,theta,C = p err = y - (A*sin(k*x+theta)**2+C) return err def peval(x,p): A,k,theta,C = p return A*sin(k*x+theta)**2+C for i in range(len(data)): dat = data[i,:] x=arange(1,17,1) y_meas = dat[2:] freq1=dat[0] freq2=dat[1] #Plotting min=x.min() max=x.max() step=(max-min)/100. xfine=arange(min,max,step) subnr=250+i+1 pylab.subplot(subnr) pylab.plot(xfine,peval(xfine,plsq[0]), 'r') pylab.errorbar(x,y_meas,yerr=sqrt(y_meas),fmt='bo') pylab.xlabel('Number [...]') pylab.ylabel('Value [...]') pylab.grid(True) pylab.legend(('Fitting', 'Measured Data'), 'upper right', shadow=True) pylab.title('Least square fit for Mira') pylab.show() ############################################## I just want the graph to be arranged properly into the window. Later i need to add a main title, a title for each graph and return the values that the computer used to fit the graph (meaning A, k, theta and C) Thanks a lot! -Julia- -- View this message in context: http://www.nabble.com/sub-plotting-10-into-the-window-tf4651852.html#a13290670 Sent from the matplotlib - users mailing list archive at Nabble.com.
On Thursday 18 October 2007 06:43, Wayne E. Harlan wrote: > First you should look at the axes() command with its arguments to > control the boundaries of the plot area inside the figure. I always use > this to maximize the use of the figure space. What is argument to do that? In API I didn't find this. > I'm not sure, though, > whether this works with the kind of plot you want. Check it out. The > other thing that is related is the aspect ratio of the plot. A pie > chart will only fill up as far as the shortest dimension available, so > from your attachment you might try increasing the height or decreasing > the width. If if decrase the width, my pie isn't rounding but eliptical. -- Romain Bignon - http://vaginus.org http://www.inl.fr
Christian Lerrahn wrote: > Hi, > when I plot 2D data with imshow() and then add a contour plot, my > contours have an offset in relation to the data. At the same time there > is white space at the edge of my plot, so I assume that it is the > imshow plot that actually gets shifted. I'm new to Python and > matplotlib, so I don't really understand that. Can anybody give me a > hint about how to get rid of this offset? In the examples subdirectory of the mpl distribution, see contour_image.py. Eric
Hi, when I plot 2D data with imshow() and then add a contour plot, my contours have an offset in relation to the data. At the same time there is white space at the edge of my plot, so I assume that it is the imshow plot that actually gets shifted. I'm new to Python and matplotlib, so I don't really understand that. Can anybody give me a hint about how to get rid of this offset? Cheers, Christian
On 10/18/07, Eric Firing <ef...@ha...> wrote: > Jeremy Conlin wrote: > > On 10/18/07, Eric Firing <ef...@ha...> wrote: > >> Jeremy Conlin wrote: > >>> On 10/17/07, Charles Seaton <cs...@st...> wrote: > >>>> Jeremy, > >>>> > >>>> I ran across the answer to this last week while searching the list for > >>>> info on datestr2num (both subjects happened to come up in the same > >>>> exchange). > >>>> > >>>> http://www.nabble.com/First-impression-from-a-new-user-tf1716894.html#a4662446 > >>>> > >>>> plot(x, y, linestyle='*steps*') > >>>> > >>>> Charles Seaton > >>> > >>> Well that's great! (I should have at least tried making such a plot > >>> before posting. Sorry.) How come I couldn't find it in the > >>> documentation? I can't find anything about available linestyles. Am > >>> I looking the wrong location? I am looking at users_guide_0.9.0.pdf > >> The user's guide tends to lag. To find the latest features, look at the > >> CHANGELOG, the examples, and the docstrings. Ipython is a big help for > >> looking at docstrings and trying things out. Are you familiar with it? > >> > >> Eric > >> > > > > I am familiar with IPython and use it all the time as a replacement > > for the standard Python interpreter. I don't always use the extra > > features it offers. I just did > > > > help pylab.plot > > Even easier: > > pylab.plot? > > And for more detail (but mostly useful for matplotlib modules and > functions rather than for their pylab wrappers), use two question marks > to view the source code. > > To see available functions or attributes, use tab completion. > > Eric > > > > > > and there it was, what the available linestyles. Again lesson > > learned, read the (available) documentation before asking the > > questions. It is sometimes confusing where to go for the > > documentation. > > > > Thanks, > > Jeremy > > Ooh, very nice. I'll try to incorporate those commands into my daily repertoire. Jeremy
Jeremy Conlin wrote: > On 10/18/07, Eric Firing <ef...@ha...> wrote: >> Jeremy Conlin wrote: >>> On 10/17/07, Charles Seaton <cs...@st...> wrote: >>>> Jeremy, >>>> >>>> I ran across the answer to this last week while searching the list for >>>> info on datestr2num (both subjects happened to come up in the same >>>> exchange). >>>> >>>> http://www.nabble.com/First-impression-from-a-new-user-tf1716894.html#a4662446 >>>> >>>> plot(x, y, linestyle='*steps*') >>>> >>>> Charles Seaton >>> >>> Well that's great! (I should have at least tried making such a plot >>> before posting. Sorry.) How come I couldn't find it in the >>> documentation? I can't find anything about available linestyles. Am >>> I looking the wrong location? I am looking at users_guide_0.9.0.pdf >> The user's guide tends to lag. To find the latest features, look at the >> CHANGELOG, the examples, and the docstrings. Ipython is a big help for >> looking at docstrings and trying things out. Are you familiar with it? >> >> Eric >> > > I am familiar with IPython and use it all the time as a replacement > for the standard Python interpreter. I don't always use the extra > features it offers. I just did > > help pylab.plot Even easier: pylab.plot? And for more detail (but mostly useful for matplotlib modules and functions rather than for their pylab wrappers), use two question marks to view the source code. To see available functions or attributes, use tab completion. Eric > > and there it was, what the available linestyles. Again lesson > learned, read the (available) documentation before asking the > questions. It is sometimes confusing where to go for the > documentation. > > Thanks, > Jeremy
On 10/18/07, Eric Firing <ef...@ha...> wrote: > Jeremy Conlin wrote: > > On 10/17/07, Charles Seaton <cs...@st...> wrote: > >> Jeremy, > >> > >> I ran across the answer to this last week while searching the list for > >> info on datestr2num (both subjects happened to come up in the same > >> exchange). > >> > >> http://www.nabble.com/First-impression-from-a-new-user-tf1716894.html#a4662446 > >> > >> plot(x, y, linestyle='*steps*') > >> > >> Charles Seaton > > > > > > Well that's great! (I should have at least tried making such a plot > > before posting. Sorry.) How come I couldn't find it in the > > documentation? I can't find anything about available linestyles. Am > > I looking the wrong location? I am looking at users_guide_0.9.0.pdf > > The user's guide tends to lag. To find the latest features, look at the > CHANGELOG, the examples, and the docstrings. Ipython is a big help for > looking at docstrings and trying things out. Are you familiar with it? > > Eric > am familiar with IPython and use it all the time as a replacement for the standard Python interpreter. I don't always use the extra features it offers. I just did help pylab.plot and there it was, what the available linestyles. Again lesson learned, read the (available) documentation before asking the questions. It is sometimes confusing where to go for the documentation. Thanks, Jeremy
Hi, I have a small problem with label. plot([0,1],[0,1]) xlabel(r'$ABCDEF$',fontsize=35) (but the size doesn't change anything) I obtain the result visible on the figure join. I think there are a problem when using latex and how the first character is handle. Thanks for matplotlib. N. PS: I'm using svn version: pylab.__version__ '1.0.4.dev4241'
John, svn works fine now. thanks. John Hunter wrote: > On 10/18/07, John Hunter <jd...@gm...> wrote: > >> You should use the "c" argument for scatter -- this controls the facecolor. >> >> scatter(x,x+0.5, c='blue', s=50, alpha=0.5) >> >> This is a bit of an anachronism from matlab compatibility. > > This is now fixed in svn, so you can use facecolor as well. Note that > for constant size and color markers, plot will be significantly faster > > ax.plot(x, x+0.5, mfc='blue', alpha=0.5, ms=20) > > JDH
On 10/18/07, John Hunter <jd...@gm...> wrote: > You should use the "c" argument for scatter -- this controls the facecolor. > > scatter(x,x+0.5, c='blue', s=50, alpha=0.5) > > This is a bit of an anachronism from matlab compatibility. This is now fixed in svn, so you can use facecolor as well. Note that for constant size and color markers, plot will be significantly faster ax.plot(x, x+0.5, mfc='blue', alpha=0.5, ms=20) JDH
On 10/18/07, Manuel Metz <mm...@as...> wrote: > It seems that the keywords facecolor (or color) and alpha can not be > used simultaniously when using "scatter": > > > import pylab > > x = pylab.npy.arange(0,10) > pylab.scatter(x,x, s=50, alpha=0.5) > pylab.scatter(x,x+0.5, facecolor='blue', s=50, alpha=0.5) > pylab.show() > > > The alpha value of the second call is not set correctly, but kept fix at > alpha=1.0. Any idea ??? You should use the "c" argument for scatter -- this controls the facecolor. scatter(x,x+0.5, c='blue', s=50, alpha=0.5) This is a bit of an anachronism from matlab compatibility. JDH
On 10/18/07, Jordan Atlas <jc...@co...> wrote: > Hello, > > I'm having some trouble figuring out how to format the numerical > labels on the tick marks of an axes. For example, in the plot linked > below, I'd like the y-axis to display using scientific notation, and I'd > like to control the precision level. I feel like this should be somehow > possible using setp(yticklabels,...) but I haven't been able to find the > relevant documentation or an example. Can someone point me in the right > direction here? You can set the formatter for the yaxis from matplotlib.ticker import FormatStrFormatter fmt = FormatStrFormatter('%1.4g') # or whatever ax.yaxis.set_major_formatter(fmt) There is also a class tickers.ScalarFormatter for scientific formatting that is customizable. You'll probably want to take a look at it. > Also, if someone has a suggestion for how to automatically avoid the > axis label ('CW') being cut off like in the attachment, let me know (I'm > letting the figure size get set automatically). The easiest way to fix this is just to move the left border of your axes over a bit fig = figure() fig.subplots_adjust(left=0.2) ax = fig.add_subplot(111) # now there is more space on the left JDH
Hello, I'm having some trouble figuring out how to format the numerical labels on the tick marks of an axes. For example, in the plot linked below, I'd like the y-axis to display using scientific notation, and I'd like to control the precision level. I feel like this should be somehow possible using setp(yticklabels,...) but I haven't been able to find the relevant documentation or an example. Can someone point me in the right direction here? Also, if someone has a suggestion for how to automatically avoid the axis label ('CW') being cut off like in the attachment, let me know (I'm letting the figure size get set automatically). Please feel free to point me to a relevant section of the manual or to a function that I might be missing. Thank you, --Jordan Here is the example: http://www.people.cornell.edu/pages/jca33/labels.pdf
It seems that the keywords facecolor (or color) and alpha can not be used simultaniously when using "scatter": import pylab x = pylab.npy.arange(0,10) pylab.scatter(x,x, s=50, alpha=0.5) pylab.scatter(x,x+0.5, facecolor='blue', s=50, alpha=0.5) pylab.show() The alpha value of the second call is not set correctly, but kept fix at alpha=1.0. Any idea ??? Manuel
Jeremy Conlin wrote: > On 10/17/07, Charles Seaton <cs...@st...> wrote: >> Jeremy, >> >> I ran across the answer to this last week while searching the list for >> info on datestr2num (both subjects happened to come up in the same >> exchange). >> >> http://www.nabble.com/First-impression-from-a-new-user-tf1716894.html#a4662446 >> >> plot(x, y, linestyle='*steps*') >> >> Charles Seaton > > > Well that's great! (I should have at least tried making such a plot > before posting. Sorry.) How come I couldn't find it in the > documentation? I can't find anything about available linestyles. Am > I looking the wrong location? I am looking at users_guide_0.9.0.pdf The user's guide tends to lag. To find the latest features, look at the CHANGELOG, the examples, and the docstrings. Ipython is a big help for looking at docstrings and trying things out. Are you familiar with it? Eric
First you should look at the axes() command with its arguments to control the boundaries of the plot area inside the figure. I always use this to maximize the use of the figure space. I'm not sure, though, whether this works with the kind of plot you want. Check it out. The other thing that is related is the aspect ratio of the plot. A pie chart will only fill up as far as the shortest dimension available, so from your attachment you might try increasing the height or decreasing the width. Wayne Romain Bignon wrote: > Hello, > > When I create a graph, margin is too wide. How can I reduce this? > > There is an example with this mail. > > Thanks. > > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. > Still grepping through log files to find problems? Stop. > Now Search log events and configuration files using AJAX and a browser. > Download your FREE copy of Splunk now >> http://get.splunk.com/ > ------------------------------------------------------------------------ > > _______________________________________________ > Matplotlib-users mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-users >
Thank you Ken, I ended up doing more or less as you suggested but it turns out that with the new pick API is actually much easier: wxmpl.EVT_POINT(self, self.GetId(), self.onPoint) self.mpl_connect('pick_event', self.onPick) def onPoint(self,event): ''' Called by the EVT_POINT of wxmpl. Generates a pick_event ''' event.axes.pick(event) def onPick(self,event): ''' Called upon a pick_event ''' print 'You picked %s' % event.ind GG On 10/15/07, Ken McIvor <mc...@ii...> wrote: > On Oct 12, 2007, at 4:28 PM, Giorgio F. Gilestro wrote: > > > > Do you know if there is a reason why I cannot succeed in generating a > > pick_event using wxmpl? > > Yes, WxMpl disables all matplotlib events to ensure that figure > zooming works correctly. I haven't had time to ensure that WxMpl will > work reliably in all cases when matplotlib's events are enabled. > > > I know I could use EVT_POINT but I need the picker event to return > > the event.ind > > Although it's a bit silly, one possible solution would be to have > your EVT_POINT callback generate a mouse event. I think something > like this might work, but I haven't tried it... > > from matplotlib.backend_bases import FigureCanvasBase > > def OnPoint(evt): > figureCanvas = evt.axis.figure.canvas > FigureCanvasBase.button_press_event(figureCanvas, evt.x, evt.y, 1) > > > Ken >
On 10/17/07, Charles Seaton <cs...@st...> wrote: > Jeremy, > > I ran across the answer to this last week while searching the list for > info on datestr2num (both subjects happened to come up in the same > exchange). > > http://www.nabble.com/First-impression-from-a-new-user-tf1716894.html#a4662446 > > plot(x, y, linestyle='*steps*') > > Charles Seaton Well that's great! (I should have at least tried making such a plot before posting. Sorry.) How come I couldn't find it in the documentation? I can't find anything about available linestyles. Am I looking the wrong location? I am looking at users_guide_0.9.0.pdf Thanks again, Jeremy
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> <html> <head> </head> <body bgcolor="#ffffff" text="#000066"> If one creates a 1V RMS sine wave, e.g. with a peak value of 1.414 or<br> peak-peak of 2.83, then computes psd, the resulting amplitude is around<br> 24 dB, yet classic theory dictates the answer ought to be 20 log(1) = 0 dB.<br> This offset seems consistent across various frequencies/sample rates/amplitudes.<br> Can someone illuminate the amplitude scaling of the psd algorithm?<br> Thanks.<br> <pre class="moz-signature" cols="80">-- </pre> </body> </html>