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
(36) |
2
(10) |
3
(8) |
4
|
5
(4) |
6
(15) |
7
(17) |
8
(3) |
9
(8) |
10
(5) |
11
(2) |
12
(5) |
13
(5) |
14
(15) |
15
(3) |
16
(10) |
17
(6) |
18
(2) |
19
(1) |
20
(11) |
21
(33) |
22
(13) |
23
(14) |
24
(15) |
25
(4) |
26
(5) |
27
(9) |
28
(12) |
29
(7) |
30
(8) |
31
(6) |
|
"Lee, Young-Jin" <yo...@uc...> writes: > Then, I realized because each bar is so narrow I can't see the color of > the bars but only outside lines (I see the colors by zooming it), which > I couldn't find a way to change the color. My question is, is there any > way either 1) to get rid of the outside lines or 2) to change the color > of the lines? Thanks much in advance! To get rid of the lines, set the linewidth property of the bars to 0; to change their color, set the edgecolor property. For example, using ipython -pylab: In [31]: a=bar([1,2,3,4],[3,1,4,1],lw=0) In [32]: setp(a[1], lw=10, ec='red') Out[32]: [None, None] Here I used the abbreviations lw and ec for linewidth and edgecolor. The first command creates a bar chart where all bars have line width zero, the second modifies one of the bars to have very thick red edges. You can experiment with the properties using the pylab commands getp and setp. -- Jouni K. Seppänen http://www.iki.fi/jks
Lee, Young-Jin wrote: > Hey guys, > > > > I’m a new guy in here and amazed by the capability Matplotlib has. I > have a question for you, which might be a result of my ignorance or the > limitation of the current Matplotlib. I’m trying to make a bar chart > with hundreds of bars at different x positions with their own y values > (so called mass spectra) and would like to have different colors for > some of them, but the bar colors were never changed to what I intended. > Then, I realized because each bar is so narrow I can’t see the color of > the bars but only outside lines (I see the colors by zooming it), which > I couldn’t find a way to change the color. My question is, is there any > way either 1) to get rid of the outside lines or 2) to change the color > of the lines? Thanks much in advance! For (1), use the linewidth=0 kwarg, e.g.: barh(pos,val, align='center', linewidth=0) Eric > > > > Young Jin > > > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > 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
Hey guys, =20 I'm a new guy in here and amazed by the capability Matplotlib has. I have a question for you, which might be a result of my ignorance or the limitation of the current Matplotlib. I'm trying to make a bar chart with hundreds of bars at different x positions with their own y values (so called mass spectra) and would like to have different colors for some of them, but the bar colors were never changed to what I intended. Then, I realized because each bar is so narrow I can't see the color of the bars but only outside lines (I see the colors by zooming it), which I couldn't find a way to change the color. My question is, is there any way either 1) to get rid of the outside lines or 2) to change the color of the lines? Thanks much in advance! =20 Young Jin =20
On 8/22/07, Tom Vaughan <to...@cr...> wrote: > Why on the YellowDog 3 system would the x-axis show up as 0 - 2.5, and > on the Ubuntu Feisty system would the x-axis show up as 2.2 - 2.4? I > am attempting to resolve an autoscale problem elsewhere, and I must of > screwed something up when I built matplotlib. But what? The only explanation that makes sense to me is that you are picking up different versions of mpl. Did you ever install from svn on any system? You can print >>> import matplotlib >>> print matplotlib.__version__ but that doesn't always help, because frequently different svn versions will print the same version number. We should adopt the numpy and scipy system of tagging the version w/ the svn revision number.... JDH
Hi, I have matplotlib 0.90.1 on YellowDog 3 PPC with Python 2.5 and all the support libraries built by hand, and matplotlib-0.90.1 on Ubuntu Feisty x86 via `aptitude install`. And let's say I have: import pylab pylab.plot([2.2, 2.3, 2.4], [0, 5, 1]) pylab.show() Why on the YellowDog 3 system would the x-axis show up as 0 - 2.5, and on the Ubuntu Feisty system would the x-axis show up as 2.2 - 2.4? I am attempting to resolve an autoscale problem elsewhere, and I must of screwed something up when I built matplotlib. But what? Thanks. -Tom
On 8/22/07, Angus McMorland <am...@gm...> wrote: > > I would like to use mpl_connect and disconnect to examine a series of 2d > > arrays in turn (with a "for" loop), one after the other: > > > > ==> at each iteration I'd like to be able to use the left mouse button > > to evaluate the sum of all x,y coordinates I select by (right) clicking > > somewhere in the present array, and then switch to the next 2d data > > array after I hit the right mouse button (button==3). I have no clue how > > to do this and the program I wrote so far is just hanging there and does > > nothing. Didn't see anything like this in the archive. > > > > Any way to get out of this? Thanks for your help. > > As a general rule of thumb, if you're using a loop like while > newoffset.stay: pass, then you're doing something wrong. Angus is right w/ resepct to mpl -- we don't have any support for blocking calls. This is a very frequent request and you are certainly right Eric to *expect* something like this to work, but in the context of multiple GUIs w/ threads it is not too easy. One could probably make tkagg work with only minor modifications to mpl, but the other GUIs would be harder becasue they are threaded. So using event handling and callbacks are the way to solve this problem, as Angus suggests in his solution, but they are harder for people to get their head around than blocking calls, so hopefully we will get support for this idiom before the end of time. JDH
Hi Eric, On 23/08/07, Eric Emsellem <ems...@ob...> wrote: > Hi > > sorry to post this again but all my attempts to solve the matplotlib > problem below failed and I desperately need this to progress. > > I would like to use mpl_connect and disconnect to examine a series of 2d > arrays in turn (with a "for" loop), one after the other: > > ==> at each iteration I'd like to be able to use the left mouse button > to evaluate the sum of all x,y coordinates I select by (right) clicking > somewhere in the present array, and then switch to the next 2d data > array after I hit the right mouse button (button==3). I have no clue how > to do this and the program I wrote so far is just hanging there and does > nothing. Didn't see anything like this in the archive. > > Any way to get out of this? Thanks for your help. As a general rule of thumb, if you're using a loop like while newoffset.stay: pass, then you're doing something wrong. This will take control of all execution and let nothing else happen. You have to do the control by switching between functions. Here's a modification to your code that I think does what you want: import numpy as n import pylab as p class offset: def __init__(self, parent) : self.parent = parent self.xc = 0. self.yc = 0. self.stay = 1 def on_click(self, event) : if event.button == 1: if event.inaxes is not None: print "Adding point %d, %d" % (event.xdata, event.ydata) self.xc += event.xdata self.yc += event.ydata elif event.button == 3: print "Switching data" self.parent.show_next() class displayer: def __init__(self): self.i = 0 self.alldata = [n.random.rand(10,10) for x in xrange(3)] self.newoffset = offset(self) self.binding = p.connect('button_press_event', self.newoffset.on_click) self.show_next() def show_next(self): if self.i < len(self.alldata): p.imshow(self.alldata[self.i]) self.i += 1 else: p.disconnect(self.binding) print self.newoffset.xc, self.newoffset.yc I hope that helps you see the concept. Angus. -- AJC McMorland, PhD Student Physiology, University of Auckland
Hi Chris, Sorry to bring it up. I know you didn't make the decision so I'll shut up about it right after I say the following: "That was a really dumb/weak reason for breaking the standard 'discussion list' format" What a pain. Greg On 8/22/07, Christopher Barker <Chr...@no...> wrote: > > Greg Willden wrote: > > It seems that the list configuration is somewhat broken. > > The reply-to header is not set in some emails sent to the list. > > This means that replies go directly to the requestors but not to the > > list as a whole. > > > > That seems pretty broken to me. > > me too, but there are folks that are convinced that this is the way to > have things set up. There was a pretty extensive discussion about it on > this list a year or so ago (but it may have been another list I'm on). > The discussion included a link to someones very well written BLOG entry > on why mailing lists should be set up without the reply-to header sent. > It was very well written and argued, but frankly, I think, based on > false assumptions. > > It comes down to this: > > Which is worse (pro-rated by how likely it is)? > > Accidentally sending what was intended as a private note to the list. > > or > > Accidentally sending what was meant as a list note to only the OP and > often ending up with many copies of the same message, as reply-to all > keeps adding each contributor to the thread. > > Note that with the current system, you have to hit "reply-to-all", which > ends up sending duplicate copies to the OP (and anyone else that has > added to the thread) unless you make a point of deleting the extra > receiver. I try to do that, but it is a pain. > > However, this has been argued out, and a decision made, so I probably > shouldn't have written this. Sorry. > > -Chris > > > > -- > Christopher Barker, Ph.D. > Oceanographer > > Emergency Response Division > NOAA/NOS/OR&R (206) 526-6959 voice > 7600 Sand Point Way NE (206) 526-6329 fax > Seattle, WA 98115 (206) 526-6317 main reception > > Chr...@no... > > ------------------------------------------------------------------------- > 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 > -- Linux. Because rebooting is for adding hardware.
Greg Willden wrote: > It seems that the list configuration is somewhat broken. > The reply-to header is not set in some emails sent to the list. > This means that replies go directly to the requestors but not to the > list as a whole. > > That seems pretty broken to me. me too, but there are folks that are convinced that this is the way to have things set up. There was a pretty extensive discussion about it on this list a year or so ago (but it may have been another list I'm on). The discussion included a link to someones very well written BLOG entry on why mailing lists should be set up without the reply-to header sent. It was very well written and argued, but frankly, I think, based on false assumptions. It comes down to this: Which is worse (pro-rated by how likely it is)? Accidentally sending what was intended as a private note to the list. or Accidentally sending what was meant as a list note to only the OP and often ending up with many copies of the same message, as reply-to all keeps adding each contributor to the thread. Note that with the current system, you have to hit "reply-to-all", which ends up sending duplicate copies to the OP (and anyone else that has added to the thread) unless you make a point of deleting the extra receiver. I try to do that, but it is a pain. However, this has been argued out, and a decision made, so I probably shouldn't have written this. Sorry. -Chris -- Christopher Barker, Ph.D. Oceanographer Emergency Response Division NOAA/NOS/OR&R (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chr...@no...
Sebastian Krieger wrote: > Hi, > > Does anyone eventually have a sample on how to make Hovmoller plots > using matplotlib? Specially with good looking time axis like Ferret does? > > Thanks > Sebastian > > > Sebastian: Don't have a hovmoller example handy, but you can see how to make a nice time axis by looking at date_demo.py at http://matplotlib.sourceforge.net/screenshots.html. Just replace the line plot with a contour plot, and there you go. -Jeff -- Jeffrey S. Whitaker Phone : (303)497-6313 Meteorologist FAX : (303)497-6449 NOAA/OAR/PSD R/PSD1 Email : Jef...@no... 325 Broadway Office : Skaggs Research Cntr 1D-124 Boulder, CO, USA 80303-3328 Web : http://tinyurl.com/5telg
It seems that the list configuration is somewhat broken. The reply-to header is not set in some emails sent to the list. This means that replies go directly to the requestors but not to the list as a whole. That seems pretty broken to me. Any list admin out there want to comment. (by replying to mat...@li... of course) Greg -- "Java: The COBOL of the 90's" -Paul Rubin on comp.lang.python
Hi, Does anyone eventually have a sample on how to make Hovmoller plots using matplotlib? Specially with good looking time axis like Ferret does? Thanks Sebastian
Hi sorry to post this again but all my attempts to solve the matplotlib problem below failed and I desperately need this to progress. I would like to use mpl_connect and disconnect to examine a series of 2d arrays in turn (with a "for" loop), one after the other: ==> at each iteration I'd like to be able to use the left mouse button to evaluate the sum of all x,y coordinates I select by (right) clicking somewhere in the present array, and then switch to the next 2d data array after I hit the right mouse button (button==3). I have no clue how to do this and the program I wrote so far is just hanging there and does nothing. Didn't see anything like this in the archive. Any way to get out of this? Thanks for your help. Eric #================= # stupid simple code just to illustrate the kind of things I would like to achieve # This does not work and just hang there... #================= import numpy as num class offset: def __init__(self) : self.xc = 0. self.yc = 0. self.stay = 1 def on_click(self, event) : if event.button == 1: if event.inaxes is not None: self.xc += event.xdata self.yc += event.ydata elif event.button == 3: self.stay = 0 data1 = num.random.rand(10,10) data2 = num.random.rand(10,10) data3 = num.random.rand(10,10) alldata = [data1, data2, data3] for i in range(len(alldata)) : imshow(alldata[i]) newoffset = offset() binding = connect('button_press_event', newoffset.on_click) while newoffset.stay : pass disconnect(binding) print newoffset.xc, newoffset.yc
I am sorry, here the better explanation: I have a scirpt to reduce data. from time to time it should bring up an interactive matplotlib figure and then when I close the window it should continue.it is important for me that the script actually stops when opening the window. The problem is (which I found out just now) I am running this in ipython and if I close the window the gtk.mainloop() stays active and doesnt let me continue my script. So i'm looking for a fucntion I can call to stop the backend thread. I know there is a thread called gtk.gdk.thread_leave but I need the appropriate TK object which is the window(or matplotlib_object or whatever) to call this function. I am happy to use another backend but I am fairly new to tk and gtk in python so I didnt see anything else. thanks in advance Wolfgang John Hunter wrote: > On 8/22/07, Wolfgang Kerzendorf <wke...@go...> wrote: > >> Is there any way I can stop the mainloop of the gtkagg backend. i know >> there is a threads_leave thing but I neec the Tk object from matplotlib. >> The problem is that my script doesnt continue after the window has been >> closed >> > > I am not exactly sure what you are after ... Do you need to use > GTKAgg at all, or can you simply set your backend to TkAgg in your > matplotlibrc and leave it at that. If for some reason you need > GTKAgg, and then need to switch to TkAgg, it may be possible to do > this with the "switch_backend" function in pylab. I have done this on > occasion with success, but it is mostly experimental. Perhaps if you > explain your use case a little better we can advise more. > >
On 8/22/07, Wolfgang Kerzendorf <wke...@go...> wrote: > Is there any way I can stop the mainloop of the gtkagg backend. i know > there is a threads_leave thing but I neec the Tk object from matplotlib. > The problem is that my script doesnt continue after the window has been > closed I am not exactly sure what you are after ... Do you need to use GTKAgg at all, or can you simply set your backend to TkAgg in your matplotlibrc and leave it at that. If for some reason you need GTKAgg, and then need to switch to TkAgg, it may be possible to do this with the "switch_backend" function in pylab. I have done this on occasion with success, but it is mostly experimental. Perhaps if you explain your use case a little better we can advise more.
Is there any way I can stop the mainloop of the gtkagg backend. i know there is a threads_leave thing but I neec the Tk object from matplotlib. The problem is that my script doesnt continue after the window has been closed thanks in advance Wolfgang
Andrew Jaffe <a.h...@gm...> writes: > I admit I don't understand the problems or the speccific code involved, > but I *think* it may be that the OSX-specific code isn't restricted to > afm files. Hence I wonder if the following is a fix: > - for f in OSXInstalledFonts(): > + for f in OSXInstalledFonts(fontext=fontext): It helps in this particular case, but I think the intention behind this code is to allow loading non-TrueType fonts even when fontext='ttf'. On OS X there are various non-TrueType font formats (dfont, otf, resource-fork fonts), at least some of which are supported by freetype, so if you always pass fontext to OSXInstalledFonts, you unnecessarily limit the fonts found to those whose filename indicates ttf format. (Macs also don't care as much about filename extensions as the rest of the world.) But I'm just guessing here as to the reasoning behind the code. Somebody else might know better? -- Jouni K. Seppänen http://www.iki.fi/jks
The script I am writing gets sometimes stuck after show(). Of course show() halts the script but when I close the window I want it to continue. Is there a sure way to kill off the pylab thread and continue like with a key press event on ESC and then calling a stop routine of the thread. Thanks in advance Wolfgang
Hi- I admit I don't understand the problems or the speccific code involved, but I *think* it may be that the OSX-specific code isn't restricted to afm files. Hence I wonder if the following is a fix: % svn diff lib/matplotlib/font_manager.py Index: lib/matplotlib/font_manager.py =================================================================== --- lib/matplotlib/font_manager.py (revision 3727) +++ lib/matplotlib/font_manager.py (working copy) @@ -229,7 +229,7 @@ fontpaths = x11FontDirectory() # check for OS X & load its fonts if present if sys.platform == 'darwin': - for f in OSXInstalledFonts(): + for f in OSXInstalledFonts(fontext=fontext): fontfiles[f] = 1 for f in get_fontconfig_fonts(fontext): It would be great if someone could confirm this and submit to svn. Andrew Jouni K. Seppänen wrote: > Eric Firing <ef...@ha...> writes: > >> I think that the problem is occurring in the last line. This remains to >> be verified. It looks like *.afm files are being found, but when >> createFontDict tries to parse them it doesn't find what it expects. > > The cause of the problem is a combination of two things: first, for > some reason the afmfiles list contains non-AFM files, which is probably > a bug; second, the AFM parser doesn't quit when faced with a malformed > file. I committed a sanity check (diff attached) in afm.py to fix the > second problem, but the first one remains. > >
When I diff the ghostscript generated eps which does not distill and =20 the ps which does. There is not much difference. I know next to nothing about postscript =20= but the differences have to do with the prolog and trailer and nothing else. %!PS-Adobe-3.0 EPSF-3.0 %%BoundingBox: 14 188 591 593 %%HiResBoundingBox: 14.933874 188.868363 590.933874 592.068363 %!PS-Adobe-3.0 %%Pages: (atend) %%BoundingBox: 17 194 594 598 %%HiResBoundingBox: 17.987999 194.507994 593.999982 597.527982 **** eps extra prolog***** %%BeginProlog save countdictstack mark newpath /showpage {} def /setpagedevice {pop} def %%EndProlog %%Page 1 1 *** eps *** %%PageTrailer %%Trailer cleartomark countdictstack exch sub { end } repeat restore %%Pages: 1 %%EOF *** ps *** %%PageTrailer %%Trailer %%Pages: 1 %%EOF On 21 Aug 2007, at 11:10 , Darren Dale wrote: > On Tuesday 21 August 2007 12:46:05 pm Jouni K. Sepp=E4nen wrote: >> Darren Dale <dd...@co...> writes: >>>> The testgs.eps (for test with ghostscript) does not convert to pdf >>>> using either apple preview or adobe distiller (the adobe log is >>>> included) >>>> It does however convert successfully with epstopdf so there is some >>>> subtle difference. >>> >>> I'm sorry, I have no idea. I guess you would have to take it up with >>> ghostscript, that is the program that is producing the file that =20 >>> adobe >>> and apple preview is having trouble with. >> >> Since this is on Mac OS X, I suspect it is the long-standing font >> problem; that is, matplotlib finds and uses some system fonts but =20 >> does >> not embed them correctly. If you force the Bitstream Vera family of >> fonts, does it work then? > > I doubt this is the case. The ghostscript distiller does not embed =20 > any fonts, > it renders the text as rasters. > > ----------------------------------------------------------------------=20= > --- > 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 =20 > 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 ********************************************************************** Samuel M. Smith Ph.D. 2966 Fort Hill Road Eagle Mountain, Utah 84005-4108 801-768-2768 voice 801-768-2769 fax ********************************************************************** "The greatest source of failure and unhappiness in the world is giving up what we want most for what we want at the moment" **********************************************************************
Hi, Is there any way to store the data of the plot into a ps or eps file ? sometimes I don't want to store both the data file and eps plot, but worried if someday later I need the specific numbers. Do I have to manipulate the ps file ? I know it's ascii, but is it dangerous ? Thanks. Lingyun
Eric Firing <ef...@ha...> writes: > I think that the problem is occurring in the last line. This remains to > be verified. It looks like *.afm files are being found, but when > createFontDict tries to parse them it doesn't find what it expects. The cause of the problem is a combination of two things: first, for some reason the afmfiles list contains non-AFM files, which is probably a bug; second, the AFM parser doesn't quit when faced with a malformed file. I committed a sanity check (diff attached) in afm.py to fix the second problem, but the first one remains. -- Jouni K. Seppänen http://www.iki.fi/jks
On 22/08/07, Geoffrey Zhu <zyz...@gm...> wrote: > On 8/20/07, Angus McMorland <am...@gm...> wrote: > > On 21/08/07, Geoffrey Zhu <zyz...@gm...> wrote: > > > Hi Everyone, > > > > > > I just started to use pylab, and there are two issues I can't figure > > > out a way to get around. > > > > > > 1. show() does not return until I close the plot window. This makes it > > > impossible to show multiple plots at the same time. How can I show > > > multiple plots? > > > > > > 2. How can I get a handle or object reference to the plot window so > > > that I can manipulate it specifically? > > > > Is this what you're after? > > > > import pylab as p > > > > f0 = p.figure() > > f1 = p.figure() > > ax0 = f0.add_subplot(111) > > ax0.plot(data) > > ax1 = f1.add_subplot(111) > > ax1.plot(otherdata) > > > > > I found some references to the API. The API seems quite different from > > > the plot interface and is considerably low-level. So am just wondering > > > if using the API is the only way to do these things. It seems to me > > > that if plot(...) can return an object reference to the chart winodw, > > > all these can easily be solved. > > > > > > Thanks, > > > Geoffrey > > Yes, this solves most of my problems, except that show() still does > not return until I close the charts. Yes, this is the problem that Bill describes about needing a separate GUI thread to allow both the plots and the shell to work simultaneously. You need to try one of his solutions to get around the issue - I highly recommend using ipython -pylab, which will take of all this completely transparently for you. A. -- AJC McMorland, PhD Student Physiology, University of Auckland
Jouni K. Seppänen <jk...@ik...> writes: > Another data point: a recent svn version of matplotlib segfaults on my > OS X system, and ktrace suggests it occurs while it is reading > CharcoalCY.dfont. Looks like a freetype bug: the following code segfaults when linked against libfreetype.6.3.10 but not when linked against libfreetype.6.3.16. Freetype has some code to read dfont files, which apparently had a bug in the older version, and this is triggered by the new code that reads in all font files.
Mark Bakker wrote: > After further anlysis, I still get the light colored lined at x=10 when > I zoom-in interactively on that line (still using TkAgg). Have you tried > zooming-in? > > I tried to zoom in on my eps and png files with the overlap, and they > look fine. > > That's all. I can live with it just fine, but it is odd. > Still would like to know what interpolation option you used. All default, out of the box. I think that is bilinear. I have to run--can't check now. Eric > Thanks, > > Mark > > On 8/21/07, * Mark Bakker* <ma...@gm... > <mailto:ma...@gm...>> wrote: > > I use TkAgg on win32, and saw the line on screen and in png and eps > files. > I tried nudging it, but that didn't work either. > So I tried the following overlap and still saw the line: > a = ones((10,10)) > imshow(a,extent=( 0.0,11.0,0.0,10.0)) > imshow(a,extent=(10.0,20.0,0.0,10.0)) > axis((0,20,0,10)) > > So I figured it had to do with the interpolation. > I used the default interpolation ('bilinear'). > When I do the above overlap with interpolation set to 'nearest', I > don't get the line! > > What interpolation were you using? > > Thanks for your help, > > Mark > > > > On 8/21/07, * Eric Firing* < ef...@ha... > <mailto:ef...@ha...>> wrote: > > Mark, > > What backend? I don't see it when I run your lines in ipython > -pylab, > with gtkagg in use (linux). > > Have you tried using floating point extents and fudging them very > slightly to overlap? > > Eric > > Mark Bakker wrote: > > Hello all - > > > > I am trying to plot two images side byside. > > The problem is that I get a white line between them. > > Even when the extent of the two images are exactly next to > eachother. > > Does anybody know how to get rid of the white line? > > Here's an easy example: > > > > from pylab import * > > a = ones((10,10)) > > imshow(a,extent=(0,10,0,10)) > > imshow(a,extent=(10,20,0,10)) > > axis((0,20,0,10)) > > > > Thanks, Mark > > > > > > > ------------------------------------------------------------------------ > > > > > > ------------------------------------------------------------------------- > > 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... > <mailto:Mat...@li...> > > https://lists.sourceforge.net/lists/listinfo/matplotlib-users > > > > > ------------------------------------------------------------------------ > > ------------------------------------------------------------------------- > 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