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
|
From: mmanu <emm...@gm...> - 2005-12-06 15:54:44
|
hi, i'm triing to install matplotlib with ubuntu breezy (amd64). An error occurs with 'python setup.py build' : gcc -pthread -fno-strict-aliasing -DNDEBUG -g -O3 -Wall -Wstrict-prototypes -fPIC -Iagg23/include -Isrc -Iswig -I/usr/include/python2.4 -c src/agg.cxx -o build/temp.linux-x86_64-2.4/src/agg.o gcc: installation problem, cannot exec 'cc1plus': No such file or directory error: command 'gcc' failed with exit status 1 have you any ideas ? thanks. mmanu |
From: Christian K. <ck...@ho...> - 2005-12-06 15:03:39
|
Darren Dale wrote: > On Tuesday 06 December 2005 09:10, Alex Gontmakher wrote: > >>Hi, >> >>I'm trying to use matplotlib solely for my plotting needs. >>Problem is, the fonts are embedded in each EPS file, and >>when I import several plots (I have tens of them...) into a >>single Latex, the resulting file is HUGE. >> >>Any suggestions? > > > There are currently two options: you can either set ps.useafm = True, or you > can set text.usetex = True in your rc settings. Since you are importing > figures into latex, I suggest the usetex option. That way, your figure fonts > can be the same as your text fonts. You'll take a bit of a speed hit with the > latter option, but in my opinion, its the only way to go for generating plots > for publication. When using tex for font rendering I noticed that parts of the text are not converted to polygons but embedded as bitmaps. That makes the files big again. Do you now how to avoid that? E.g. using the r'$C_{12}$ will produce two images for the numbers and a polygon for the 'C'. Regards, Christian |
From: Darren D. <dd...@co...> - 2005-12-06 14:48:52
|
On Tuesday 06 December 2005 09:10, Alex Gontmakher wrote: > Hi, > > I'm trying to use matplotlib solely for my plotting needs. > Problem is, the fonts are embedded in each EPS file, and > when I import several plots (I have tens of them...) into a > single Latex, the resulting file is HUGE. > > Any suggestions? There are currently two options: you can either set ps.useafm = True, or you can set text.usetex = True in your rc settings. Since you are importing figures into latex, I suggest the usetex option. That way, your figure fonts can be the same as your text fonts. You'll take a bit of a speed hit with the latter option, but in my opinion, its the only way to go for generating plots for publication. Darren |
From: Alex G. <gs...@cs...> - 2005-12-06 14:33:12
|
Hi, I'm trying to use matplotlib solely for my plotting needs. Problem is, the fonts are embedded in each EPS file, and when I import several plots (I have tens of them...) into a single Latex, the resulting file is HUGE. Any suggestions? Thanks, Alex |
From: Mike D. <mi...@de...> - 2005-12-05 13:35:48
|
Thanks guys - downloading as I sleep :) Regards mike Tim Leslie wrote: > It sounds like what you're after would be better done with the graphviz > set of programs. > > http://www.graphviz.org/ > > I've used it a couple of times to do various things and it's a pretty > amazing package. I don't know of any python libraries for it, but I havn't > really looked. Let us know if this meets your needs. > > Cheers > > Tim Gary Ruben wrote: > Hi Mike, > Take a look at pydot <http://dkbza.org/pydot.html>. I think John Hunter > may have used this in the matplotlib manual. > There's an ER diagram in the Graphviz (which pydot wraps) examples: > <http://www.graphviz.org/Gallery/undirected/ER.html> > Enjoy the conference. I'm too cheap to attend :-( > Gary Ruben (from Melbourne) > > Mike Dewhirst wrote: > >> Hi all >> >> Just dropped in to your list after drawing a blank in your archives. I >> am attending an Open Source Developers Conference in Melbourne as we >> speak and got a referral to you from an admirer. >> >> I'm looking for a Python (I'm new to python and graphics sw) module to >> visualise subsets of a database of related entities by printing boxes >> joined by lines. >> >> The entities are linked with named n:m relationships and I'd like to >> select one and display it in a box (with the entity name) and all >> related entities likewise in boxes linked to each other by lines >> representing the relationships tagged with the names of those >> relationships. >> >> I'm thinking I need some clever stuff to ensure as few lines as >> possible cross and mess up the visualisation. >> >> At first glance I would say we have a mismatch and your very >> impressive software is probably overkill for what I want. If I'm on >> the wrong tram with matplotlib I'd appreciate a redirect. Otherwise, >> if anyone is prepared to say matplotlib is the way to go I'll download >> it and start playing. >> >> Thanks heaps >> >> mike > > > > |
From: Gary R. <gr...@bi...> - 2005-12-05 12:52:59
|
Hi Mike, Take a look at pydot <http://dkbza.org/pydot.html>. I think John Hunter may have used this in the matplotlib manual. There's an ER diagram in the Graphviz (which pydot wraps) examples: <http://www.graphviz.org/Gallery/undirected/ER.html> Enjoy the conference. I'm too cheap to attend :-( Gary Ruben (from Melbourne) Mike Dewhirst wrote: > Hi all > > Just dropped in to your list after drawing a blank in your archives. I > am attending an Open Source Developers Conference in Melbourne as we > speak and got a referral to you from an admirer. > > I'm looking for a Python (I'm new to python and graphics sw) module to > visualise subsets of a database of related entities by printing boxes > joined by lines. > > The entities are linked with named n:m relationships and I'd like to > select one and display it in a box (with the entity name) and all > related entities likewise in boxes linked to each other by lines > representing the relationships tagged with the names of those > relationships. > > I'm thinking I need some clever stuff to ensure as few lines as possible > cross and mess up the visualisation. > > At first glance I would say we have a mismatch and your very impressive > software is probably overkill for what I want. If I'm on the wrong tram > with matplotlib I'd appreciate a redirect. Otherwise, if anyone is > prepared to say matplotlib is the way to go I'll download it and start > playing. > > Thanks heaps > > mike |
From: <J.B...@if...> - 2005-12-05 12:44:52
|
Hi, I' ve just started with matplotlib for the first time. After installation I get the following error: >>>from pylab import * ... /usr/local/lib/python2.4/site-packages/matplotlib/backends/backend_gtk.py 4 def fn_name(): return sys._getframe(1).f_code.co_name 5 ----> 6 import gobject 7 import gtk; gdk = gtk.gdk 8 import pango ImportError: No module named gobject If someone has seen this befor, please tell me how to solve the problem... cheers Jens |
From: Mike D. <mi...@de...> - 2005-12-05 11:59:06
|
Hi all Just dropped in to your list after drawing a blank in your archives. I am attending an Open Source Developers Conference in Melbourne as we speak and got a referral to you from an admirer. I'm looking for a Python (I'm new to python and graphics sw) module to visualise subsets of a database of related entities by printing boxes joined by lines. The entities are linked with named n:m relationships and I'd like to select one and display it in a box (with the entity name) and all related entities likewise in boxes linked to each other by lines representing the relationships tagged with the names of those relationships. I'm thinking I need some clever stuff to ensure as few lines as possible cross and mess up the visualisation. At first glance I would say we have a mismatch and your very impressive software is probably overkill for what I want. If I'm on the wrong tram with matplotlib I'd appreciate a redirect. Otherwise, if anyone is prepared to say matplotlib is the way to go I'll download it and start playing. Thanks heaps mike |
From: John H. <jdh...@ac...> - 2005-12-04 23:48:18
|
>>>>> "Chris" == Chris Fonnesbeck <fon...@gm...> writes: Chris> I think the correct syntax is "from scipy import fftpack", Chris> etc. I made some changes to support the new scipy in the numerix layer. You may want to update from CVS and try again. There still appears to be a problem with the color mapping code, but this is the only one I am aware of after light testing. Checking in lib/matplotlib/numerix/mlab/__init__.py; /cvsroot/matplotlib/matplotlib/lib/matplotlib/numerix/mlab/__init__.py,v <-- __init__.py new revision: 1.3; previous revision: 1.2 or later. JDH |
From: John H. <jdh...@ac...> - 2005-12-04 23:15:27
|
>>>>> "Christian" == Christian Kristukat <ck...@ho...> writes: Christian> John Hunter wrote: >>>>>>> "Christian" == Christian Kristukat <ck...@ho...> >>>>>>> writes: Christian> Hi, interpolation seems not to be supported for pcolor Christian> plots. Is that true? I want to plot nonaequidistant Christian> gridded data, so imshow is not the right choice. Using Christian> contourf with a large number of contour levels works Christian> fine but the eps output is huge. I'd prefer to have the Christian> image embedded as bitmap in an eps, that's why I'd like Christian> to use pcolor. Regards, Christian >> Nicholas Young contributed a patch which supports a >> NonUniformImage Make sure you have the most recent CVS, eg Christian> Thank you, that is what I looked for. However it is Christian> not possible to save ps/eps files with the current cvs Christian> matplotlib. It looks like some indention problems in Christian> backend_ps.py around line 240. Yep, try updating from CVS again. I just fixed this Checking in lib/matplotlib/backends/backend_ps.py; /cvsroot/matplotlib/matplotlib/lib/matplotlib/backends/backend_ps.py,v <-- backend_ps.py new revision: 1.72; previous revision: 1.71 or later. JDH |
From: Christian K. <ck...@ho...> - 2005-12-04 16:09:13
|
John Hunter wrote: >>>>>>"Christian" == Christian Kristukat <ck...@ho...> writes: > > > Christian> Hi, interpolation seems not to be supported for pcolor > Christian> plots. Is that true? I want to plot nonaequidistant > Christian> gridded data, so imshow is not the right choice. Using > Christian> contourf with a large number of contour levels works > Christian> fine but the eps output is huge. I'd prefer to have the > Christian> image embedded as bitmap in an eps, that's why I'd like > Christian> to use pcolor. Regards, Christian > > > Nicholas Young contributed a patch which supports a NonUniformImage > > Make sure you have the most recent CVS, eg Thank you, that is what I looked for. However it is not possible to save ps/eps files with the current cvs matplotlib. It looks like some indention problems in backend_ps.py around line 240. Regards, Christian |
From: Chris F. <fon...@gm...> - 2005-12-04 15:18:23
|
On 12/3/05, mat...@li... <matplotlib-user= s- > > > > > > Chris, are you using Daishi's patches? I'm not quite sure if they're i= n > > CVS yet, but it's certain that you can NOT build mpl 0.85 + scipy_core > > without them. > > Just tried it. One issue arises with the import syntax in matplotlib/numerix/fft/__init__.py: 7 elif which[0] =3D=3D "scipy": ----> 8 from scipy.fftpack import * global scipy.fftpack =3D undefined I think the correct syntax is "from scipy import fftpack", etc. -- Chris Fonnesbeck Atlanta, GA |
From: Eric F. <ef...@ha...> - 2005-12-03 23:36:06
|
Best to hold off for a little while. The patch was committed to CVS, but turned out to have a major problem, so John is working on it. Eric Fernando Perez wrote: > Chris Fonnesbeck wrote: > >> I am trying to compile matplotlib with scipy_core (latest release), >> rather than Numeric or nunmarray. However, I get the following error >> when trying to build: >> >> Traceback (most recent call last): >> File "setup.py", line 110, in ? >> raise RuntimeError("You must install Numeric, numarray, or both to >> build matplotlib") >> RuntimeError: You must install Numeric, numarray, or both to build >> matplotlib >> >> Is there no way to base matplotlib on scipy_core? > > > Chris, are you using Daishi's patches? I'm not quite sure if they're in > CVS yet, but it's certain that you can NOT build mpl 0.85 + scipy_core > without them. > > Cheers, > > f > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ > Matplotlib-users mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-users |
From: Fernando P. <Fer...@co...> - 2005-12-03 23:27:43
|
Chris Fonnesbeck wrote: > I am trying to compile matplotlib with scipy_core (latest release), > rather than Numeric or nunmarray. However, I get the following error > when trying to build: > > Traceback (most recent call last): > File "setup.py", line 110, in ? > raise RuntimeError("You must install Numeric, numarray, or both to > build matplotlib") > RuntimeError: You must install Numeric, numarray, or both to build matplotlib > > Is there no way to base matplotlib on scipy_core? Chris, are you using Daishi's patches? I'm not quite sure if they're in CVS yet, but it's certain that you can NOT build mpl 0.85 + scipy_core without them. Cheers, f |
From: Chris F. <fon...@gm...> - 2005-12-03 22:34:02
|
I am trying to compile matplotlib with scipy_core (latest release), rather than Numeric or nunmarray. However, I get the following error when trying to build: Traceback (most recent call last): File "setup.py", line 110, in ? raise RuntimeError("You must install Numeric, numarray, or both to build matplotlib") RuntimeError: You must install Numeric, numarray, or both to build matplotl= ib Is there no way to base matplotlib on scipy_core? Thanks, -- Chris Fonnesbeck Atlanta, GA |
From: Matt N. <new...@ca...> - 2005-12-03 19:55:05
|
Hi Ken, That's nice, and coordinated zooming of separate maps is certainly a good feature, but that's not what I had in mind. Sorry I was imprecise and probably hurr= ied. The case is to help visualize L maps of 'element' values that share the same pixel grid (NxM). You make a LxL (in your case 3x3) grid and in each diagonal grid i =3D 1,...L, you draw the map for the ith element. On the off-diagonal cells you draw a 2d plot of pixel intensities for a pair of element: value in element j v. value in element i for all NxM pixels. If elemetns i and j are highly correlated, this plot is a straight line, if they are uncorrelated it's a blob. There may be multiple trends that show (several points with high value for i and lower value for j, say). I think each of the correlation plots is what mpl calls a scatterplot with parameter 's' a scalar. The correlation plot shows trends between element at the expense of spatial information. The maps of individual element intensities shows spatial information at the expense of showing trends between elements. But if you could highlight or mask out selected pixels on a map or regions on a correlation plot (with a rubberband box) and have those those pixels light up or change color on other the maps and 2-element correlation plots, then you can better understand the spatial and correlation data. Does that make sense? I say I believe this would be better handled by GUI code than directly in mpl because someone has to keep track of the pixels for the correlation plot data, then change some set of plot attribute (color, symbol, etc) for those pixels on _all_ the correlation plots and false-color maps. That is, the series of plots has to be managed and altered as a unit in a way that is depends on the data, not by the plot characteristics alone. And presumably the GUI would allow you to change the color used to 'highlight' the selected points. I'm sure it _could_ be done other ways, and perhaps I'm missing something.=20 Anyway, what's wrong with having multiple wx.Panel each of which has a Figure.Axes on it? That's one example.... What about linking together plots in different frames or having draggable panels so that a user can orgranize them on the desktop as they choose? This doesn't have a lot to do with the 'should I use MPlot or wxMPL?' question, and all I'm saying is that as plots get more complicated and have more complex user interaction, some interactions will most naturally be handled at the GUI level. Sorry to stir up flames and run..... --Matt PS: Chris Barker asked: > Matt Newville wrote: > > the users of > > the library should probably not have to know anything about > > matplotlib, because they're going to be asking "I'm writing this wx > > Application and want to include a graph -- what should I use?". > >Huh? to put a graph in your app, you'd need to know the API to create >and manipulate that graph, That API should be MPL's API, why write and >document another one? Well MPlot and wxMPL both did just that (create other APIs). wxMPL is very close (derived from) MPL but it's not identical. I do think the MPL API is a little complicated if all you want to do is make a 2D line plot. With MPlot, it's: plotter =3D MPlot.PlotPanel(...) plotter.plot(x2,y2) plotter.oplot(x2,y2) and MPlot somehow neglects to make the user turn on or select how zooming works, turn on or place the legend (that's a user-configuration) or reveal that a PlotPanel has a FigureCanvas has a Figure which has an Axes which plot()s. Yes, it is less general than MPL, but it's simpler to use and includes functionality that MPL does not have. It's simply a different thing: it's not MPL, but it does use MPL to achieve its ends. So a wxPython plotting widget based on MPL doesn't need to expose the MPL API. If you want the MPL API, it already exists. I used this for MPlot (nothing else existed) -- it works fine. One of the questions here is whether it might be worth it to use the additional layer of wxMPL in MPlot. I could be convinced, and would not mind if someone else did this, but I'm not sure how big the gain would be. |
From: John H. <jdh...@ac...> - 2005-12-03 13:20:04
|
>>>>> "Christian" == Christian Kristukat <ck...@ho...> writes: Christian> Hi, interpolation seems not to be supported for pcolor Christian> plots. Is that true? I want to plot nonaequidistant Christian> gridded data, so imshow is not the right choice. Using Christian> contourf with a large number of contour levels works Christian> fine but the eps output is huge. I'd prefer to have the Christian> image embedded as bitmap in an eps, that's why I'd like Christian> to use pcolor. Regards, Christian Nicholas Young contributed a patch which supports a NonUniformImage Make sure you have the most recent CVS, eg Checking in lib/matplotlib/image.py; /cvsroot/matplotlib/matplotlib/lib/matplotlib/image.py,v <-- image.py new revision: 1.25; previous revision: 1.24 done or later Below is an example. from pylab import figure, show import matplotlib.numerix as nx from matplotlib.image import NonUniformImage x = nx.arange(-4, 4, 0.005) y = nx.arange(-4, 4, 0.005) print 'Size %d points' % (len(x) * len(y)) z = nx.sqrt(x[nx.NewAxis,:]**2 + y[:,nx.NewAxis]**2) fig = figure() ax = fig.add_subplot(111) im = NonUniformImage(ax, extent=(-4,4,-4,4)) im.set_data(x, y, z) ax.images.append(im) ax.set_xlim(-4,4) ax.set_ylim(-4,4) fig2 = figure() ax = fig2.add_subplot(111) x2 = x**3 im = NonUniformImage(ax, extent=(-64,64,-4,4)) im.set_data(x2, y, z) ax.images.append(im) ax.set_xlim(-64,64) ax.set_ylim(-4,4) show() |
From: Helge A. <he...@gm...> - 2005-12-03 11:25:12
|
On 12/3/05, Willi Richert <w.r...@gm...> wrote: > Hi, > > I tried that but got: > python plot.py > file h433x560.gz loaded and given shape (433, 560) > data ok so you got the data loaded, try commenting out one of the below lines near the end until you see something, you probably hit a bug in one of the qt routines ... hsv() contourf(x, y, h, levels) colorbar(clabels=3Dlevels[::8]) axis([0, im, 0, jm] ) axis('scaled') pldj(seg) ... I use the gtk backend btw. Helge |
From: Willi R. <w.r...@gm...> - 2005-12-03 10:26:43
|
Hi, I tried that but got: python plot.py file h433x560.gz loaded and given shape (433, 560) data ok Traceback (most recent call last): File=20 "/usr/lib/python2.3/site-packages/matplotlib/backends/backend_qtagg.py", li= ne=20 75, in paintEvent FigureCanvasAgg.draw( self ) File "/usr/lib/python2.3/site-packages/matplotlib/backends/backend_agg.py= ",=20 line 383, in draw self.figure.draw(renderer) File "/usr/lib/python2.3/site-packages/matplotlib/figure.py", line 520, i= n=20 draw for a in self.axes: a.draw(renderer) File "/usr/lib/python2.3/site-packages/matplotlib/axes.py", line 1441, in= =20 draw self.yaxis.draw(renderer) File "/usr/lib/python2.3/site-packages/matplotlib/axis.py", line 562, in= =20 draw tick.draw(renderer) File "/usr/lib/python2.3/site-packages/matplotlib/axis.py", line 162, in= =20 draw if self.label2On: self.label2.draw(renderer) File "/usr/lib/python2.3/site-packages/matplotlib/text.py", line 854, in= =20 draw self._mytext.draw(renderer) File "/usr/lib/python2.3/site-packages/matplotlib/text.py", line 339, in= =20 draw bbox, info =3D self._get_layout(renderer) File "/usr/lib/python2.3/site-packages/matplotlib/text.py", line 264, in= =20 _get_layout xys =3D [self._transform.inverse_xy_tup( xy ) for xy in zip(tx, ty)] RuntimeError: Transformation is not invertible Traceback (most recent call last): File=20 "/usr/lib/python2.3/site-packages/matplotlib/backends/backend_qtagg.py", li= ne=20 75, in paintEvent FigureCanvasAgg.draw( self ) File "/usr/lib/python2.3/site-packages/matplotlib/backends/backend_agg.py= ",=20 line 383, in draw self.figure.draw(renderer) File "/usr/lib/python2.3/site-packages/matplotlib/figure.py", line 520, i= n=20 draw for a in self.axes: a.draw(renderer) File "/usr/lib/python2.3/site-packages/matplotlib/axes.py", line 1441, in= =20 draw self.yaxis.draw(renderer) File "/usr/lib/python2.3/site-packages/matplotlib/axis.py", line 562, in= =20 draw tick.draw(renderer) File "/usr/lib/python2.3/site-packages/matplotlib/axis.py", line 162, in= =20 draw if self.label2On: self.label2.draw(renderer) File "/usr/lib/python2.3/site-packages/matplotlib/text.py", line 854, in= =20 draw self._mytext.draw(renderer) File "/usr/lib/python2.3/site-packages/matplotlib/text.py", line 339, in= =20 draw bbox, info =3D self._get_layout(renderer) File "/usr/lib/python2.3/site-packages/matplotlib/text.py", line 264, in= =20 _get_layout xys =3D [self._transform.inverse_xy_tup( xy ) for xy in zip(tx, ty)] RuntimeError: Transformation is not invertible Traceback (most recent call last): File=20 "/usr/lib/python2.3/site-packages/matplotlib/backends/backend_qtagg.py", li= ne=20 75, in paintEvent FigureCanvasAgg.draw( self ) File "/usr/lib/python2.3/site-packages/matplotlib/backends/backend_agg.py= ",=20 line 383, in draw self.figure.draw(renderer) File "/usr/lib/python2.3/site-packages/matplotlib/figure.py", line 520, i= n=20 draw for a in self.axes: a.draw(renderer) File "/usr/lib/python2.3/site-packages/matplotlib/axes.py", line 1441, in= =20 draw self.yaxis.draw(renderer) File "/usr/lib/python2.3/site-packages/matplotlib/axis.py", line 562, in= =20 draw tick.draw(renderer) File "/usr/lib/python2.3/site-packages/matplotlib/axis.py", line 162, in= =20 draw if self.label2On: self.label2.draw(renderer) File "/usr/lib/python2.3/site-packages/matplotlib/text.py", line 854, in= =20 draw self._mytext.draw(renderer) File "/usr/lib/python2.3/site-packages/matplotlib/text.py", line 339, in= =20 draw bbox, info =3D self._get_layout(renderer) File "/usr/lib/python2.3/site-packages/matplotlib/text.py", line 264, in= =20 _get_layout xys =3D [self._transform.inverse_xy_tup( xy ) for xy in zip(tx, ty)] RuntimeError: Transformation is not invertible QWidget (QWidget figure): deleted while being painted QPaintDevice: Cannot destroy paint device that is being painted Any hint how to solve this? My installation: =46C3 matplotlib-0.85 PyQt-3.15-0.1.fc3.kde PyQt-qscintilla-3.15-0.1.fc3.kde python-2.3.4-13.1 scipy_version: '0.3.2' Thanks, wr Am Freitag, 2. Dezember 2005 20:48 schrieb Helge Avlesen: > On 12/1/05, Charlie Moad <cw...@gm...> wrote: > > It would help if you were more specific. Are you referring to > > animation or static images? I can generate a million point scatter > > plot in under a minute, and I would consider this pretty good for a > > general purpose plotting package. > > Hi matplotlib'ers! > while the end result in matplotlib is starting to "get there", the speed = is > not yet where it has to be to be useful IMO. I hereby post a little > challenge for the matplotlib developers; > > get the actual plotting time (from the first plot command until show is > done) on the below dataset down to less than a second,(including the quiv= er > command in the plot.py file). > > download the 3 files here (ca 600kb in total) > > http://www.ii.uib.no/~avle/slow1/ > > execfile('plot.py') to plot the dataset (works for me with cvs as of > today). the first part of the file is just some convenience funcs for > loading the data. the plotting happen near the end. > > this is a moderately sized grid, 433x560 cells (those of you into > oceanography may recognize the area). what I observe on my pentium > 2.54ghz linux box: > > -after "data ok" on screen, it takes ca15s to render. pygist uses < 0.5s > -zoom operations take ca 5s. pygist is "instant". > -you don't want to wait for an additional quiver layer. it must take > minutes to finish. pygist is instant. with quiver, also zooming is > equally slow, the ui freeze for ages. > -often one wants to add contours from other fields on top of this, in > pygist this adds no > visible delay, matplotlib easily doubles the rendering time. > > typical usage for me is to load many such datasets, and do a lot of > zoom in/out/pan to various features, modify colors/levels, add > velocity vectors etc. currently this is quite > painful in matplotlib, as one zoom operation on realistic datasets > easily takes 10 seconds on a multi ghz machine. pygist is very fast, > even on a 400mhz laptop, memory usage is also a lot lower. > > so, I think matplotlib is a great effort, and shows a lot of promise, but > for realistic use, it is (at least for me) still far too slow! > > Helge > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log > files for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_idv37&alloc_id=16865&op=CCk > _______________________________________________ > Matplotlib-users mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-users =2D-=20 Gruss, wr =2D- Dipl.-Inform. Willi Richert C-LAB - Cooperative Computing & Communication Laboratory der Universit=E4t Paderborn und Siemens =46U.323 =46=FCrstenallee 11 D-33102 Paderborn Tel: +49 5251 60 6120 =46ax: +49 5251 60 6165 http://www.c-lab.de |
From: Eric F. <ef...@ha...> - 2005-12-03 00:43:53
|
Chris, Christopher Barker wrote: > Ken McIvor wrote: > >> I haven't really given it much thought. Most people presumably use >> MPL from IPython or scripts via pylab, so focusing documentation >> efforts on it make sense. > > > Not really. Most people use pylab, because that's what's well > documented, not the other way around. Also, a lot of us have matlab > experience, so pylab is easier that way. Don't understimate the importance of this group of users, present and potential. For a lot of people doing a lot of things, the Matlab/pylab approach works very well. Sometimes OO programming is a good way to go, but it is not the best approach in all cases. One of the strengths of python itself is that it works fine with or without OO style; mpl brings that strength to 2D graphics. Eric |
From: Ken M. <mc...@ii...> - 2005-12-03 00:28:25
|
On 12/02/05 15:20, Matt Newville wrote: <snip> > At each cell along the diagonals of the grid is a NxM false color map for > an element's intensity, the off-diagonal cells have the correlation plots > for each i,j pair of elements. How are you planning on implementing the correlation plots? <snip> > I humbly submit that this would be best handled at the GUI level. I disagree, and am willing to put my money where my mouth is! :-) Ken P.S. Watch out: to unzoom, you have to right-click on the same axes you zoomed in on. This is a bug. |
From: Christopher B. <Chr...@no...> - 2005-12-03 00:10:53
|
Matt Newville wrote: > the users of > the library should probably not have to know anything about > matplotlib, because they're going to be asking "I'm writing this wx > Application and want to include a graph -- what should I use?". Huh? to put a graph in your app, you'd need to know the API to create and manipulate that graph, That API should be MPL's API, why write and document another one? -Chris -- Christopher Barker, Ph.D. Oceanographer NOAA/OR&R/HAZMAT (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chr...@no... |
From: Christopher B. <Chr...@no...> - 2005-12-02 23:52:44
|
Ken McIvor wrote: > I haven't really given it much thought. Most people presumably use MPL > from IPython or scripts via pylab, so focusing documentation efforts on > it make sense. Not really. Most people use pylab, because that's what's well documented, not the other way around. Also, a lot of us have matlab experience, so pylab is easier that way. That being said, I don't like it much, I'd much rather have a nice, pythonic interface. I don't see any reason that a good OO API couldn't be just as effective for quick scripting as the current pylab one. I'd be happy not to have to keep track of which is the current axis, and keep having to call gca() and friends. > I think that getting a good OO API manual would really > improve things for application developers, but might be hard to justify > in the big-picture. I think application developers are a big part of the big picture, in fact. I had the idea of writing a version of the MPL manual using all OO syntax. I'd still like to do that. It would provide a useful document, and be a good test bed for what features really are miss or are more awkward to do with an OO style. Maybe one of these days I'll actually work on it! Chris -- Christopher Barker, Ph.D. Oceanographer NOAA/OR&R/HAZMAT (206) 526-6959 voice 7600 Sand Point Way NE (206) 526-6329 fax Seattle, WA 98115 (206) 526-6317 main reception Chr...@no... |
From: Matt N. <new...@ca...> - 2005-12-02 21:20:10
|
Ken, >>>That being said, it would be frustrating if you had to periodically rewr= ite >>>the user interaction code to add support new things, like subplots and >>>overlapping Axes. Providing this kind of support initially was an impor= tant >>>goal while writing WxMpl. >> >> Oh the 'user-level support code' is definitely the larger part of the >> work for adding any plot type. > >I should have been more specific and said "plot-level user interaction cod= e, >like zooming". For example, adding support for subplots means you need to= add >support for picking out which Axes object the user has drawn the selection >over and rejecting the selection if it overlaps multiple Axes. I think that's just the tip of the iceberg. If you have multiple 'Axes' -- I'd call them multiple graphs --- in an application, the application writer may very well want to let the user decide which plot goes to which graph. How would this be handled? Well, at the wxMPL/MPlot layer --- which means it does not have to be at the mpl layer. If multiple graphs were handled as each one being an instance of a Plotting Panel, that would probably seem quite natural to a wxPython author. They could be layed out anyway you'd like (they wouldn't have to be contiguous or even on the same frame) and the wxPython author could handle wehre 'the blue trace in graph 1' was the same as 'the green trace in graph 2' or scales of two graphs were somehow related. When you take the view of a Toolkit-aware programmer trying to add graphics to their application, the details of the mpl implementation seem less important and a few of its more whizbang features seem pointless, For multi-valued maps as with x-ray fluorescence (that is, a map that is L x N x M for L elements and N x M spatial pixels with L ~=3D 10, N ~=3D M ~=3D 100) whic= h I look at all the time, I very much want a LxL grid (or pick a subset of the L elements and have an L' x L' grid) of graphs that W.S. Cleveland (in 'The Elements of Graphing Data') called "ScatterPlots" (that term has a different connotation now): At each cell along the diagonals of the grid is a NxM false color map for an element's intensity, the off-diagonal cells have the correlation plots for each i,j pair of elements. The user can highlight any patch on any sub-graph and the data points falling in that region are highlighted on all the other graphs. So one can pick out the all the points with highest As levels, and see immediately what the Fe and Zn levels are at those points. I humbly submit that this would be best handled at the GUI level. --Matt |
From: Ken M. <mc...@ii...> - 2005-12-02 20:47:06
|
On 12/02/05 14:11, Matt Newville wrote: > Ken wrote: >>I can't think of any features that can't be wrapped away into a higher level >>interface, at least hypothetically. Things like creating two subplots that >>share an X axis (so they zoom together) would be a bit hairy, but I'm sure it >>could be done. > > Oh, well I think this would get so application specific that it would > be just as easy to do it at the GUI level than at the MPL level. That's possible, but there is already a quick and well-documented way to do it at the MPL level. Situations like that, where there's already a backend-portable way to do things, are what WxMpl tries to cater. >>That being said, it would be frustrating if you had to periodically rewrite >>the user interaction code to add support new things, like subplots and >>overlapping Axes. Providing this kind of support initially was an important >>goal while writing WxMpl. > > Oh the 'user-level support code' is definitely the larger part of the > work for adding any plot type. I should have been more specific and said "plot-level user interaction code, like zooming". For example, adding support for subplots means you need to add support for picking out which Axes object the user has drawn the selection over and rejecting the selection if it overlaps multiple Axes. Ken |