Menu
▾
▴
matplotlib-devel — matplotlib developers
You can subscribe to this list here.
| 2003 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
(1) |
Nov
(33) |
Dec
(20) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2004 |
Jan
(7) |
Feb
(44) |
Mar
(51) |
Apr
(43) |
May
(43) |
Jun
(36) |
Jul
(61) |
Aug
(44) |
Sep
(25) |
Oct
(82) |
Nov
(97) |
Dec
(47) |
| 2005 |
Jan
(77) |
Feb
(143) |
Mar
(42) |
Apr
(31) |
May
(93) |
Jun
(93) |
Jul
(35) |
Aug
(78) |
Sep
(56) |
Oct
(44) |
Nov
(72) |
Dec
(75) |
| 2006 |
Jan
(116) |
Feb
(99) |
Mar
(181) |
Apr
(171) |
May
(112) |
Jun
(86) |
Jul
(91) |
Aug
(111) |
Sep
(77) |
Oct
(72) |
Nov
(57) |
Dec
(51) |
| 2007 |
Jan
(64) |
Feb
(116) |
Mar
(70) |
Apr
(74) |
May
(53) |
Jun
(40) |
Jul
(519) |
Aug
(151) |
Sep
(132) |
Oct
(74) |
Nov
(282) |
Dec
(190) |
| 2008 |
Jan
(141) |
Feb
(67) |
Mar
(69) |
Apr
(96) |
May
(227) |
Jun
(404) |
Jul
(399) |
Aug
(96) |
Sep
(120) |
Oct
(205) |
Nov
(126) |
Dec
(261) |
| 2009 |
Jan
(136) |
Feb
(136) |
Mar
(119) |
Apr
(124) |
May
(155) |
Jun
(98) |
Jul
(136) |
Aug
(292) |
Sep
(174) |
Oct
(126) |
Nov
(126) |
Dec
(79) |
| 2010 |
Jan
(109) |
Feb
(83) |
Mar
(139) |
Apr
(91) |
May
(79) |
Jun
(164) |
Jul
(184) |
Aug
(146) |
Sep
(163) |
Oct
(128) |
Nov
(70) |
Dec
(73) |
| 2011 |
Jan
(235) |
Feb
(165) |
Mar
(147) |
Apr
(86) |
May
(74) |
Jun
(118) |
Jul
(65) |
Aug
(75) |
Sep
(162) |
Oct
(94) |
Nov
(48) |
Dec
(44) |
| 2012 |
Jan
(49) |
Feb
(40) |
Mar
(88) |
Apr
(35) |
May
(52) |
Jun
(69) |
Jul
(90) |
Aug
(123) |
Sep
(112) |
Oct
(120) |
Nov
(105) |
Dec
(116) |
| 2013 |
Jan
(76) |
Feb
(26) |
Mar
(78) |
Apr
(43) |
May
(61) |
Jun
(53) |
Jul
(147) |
Aug
(85) |
Sep
(83) |
Oct
(122) |
Nov
(18) |
Dec
(27) |
| 2014 |
Jan
(58) |
Feb
(25) |
Mar
(49) |
Apr
(17) |
May
(29) |
Jun
(39) |
Jul
(53) |
Aug
(52) |
Sep
(35) |
Oct
(47) |
Nov
(110) |
Dec
(27) |
| 2015 |
Jan
(50) |
Feb
(93) |
Mar
(96) |
Apr
(30) |
May
(55) |
Jun
(83) |
Jul
(44) |
Aug
(8) |
Sep
(5) |
Oct
|
Nov
(1) |
Dec
(1) |
| 2016 |
Jan
|
Feb
|
Mar
(1) |
Apr
|
May
|
Jun
(2) |
Jul
|
Aug
(3) |
Sep
(1) |
Oct
(3) |
Nov
|
Dec
|
| 2017 |
Jan
|
Feb
(5) |
Mar
|
Apr
|
May
|
Jun
|
Jul
(3) |
Aug
|
Sep
(7) |
Oct
|
Nov
|
Dec
|
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Phil E. <pel...@gm...> - 2014-12-22 11:21:16
|
Thanks for all the contributions so far. Looks like matplotlib is blessed with people who are far more knowledgeable than I on the subject, and I'd say we were pretty much at a consensus on requirements. Given these requirements, what we need is some proposed colormaps - Max's approach of generating an optimal solution in LAB space sounds interesting, as do the other approaches of minimising some parameters of existing colormaps. To facilitate this discussion, do we need a repository of proposed colormaps so that we can compare like with like? I notice that Mike Bostock has an interesting post to show various color spaces in d3.js which may be of interest http://bl.ocks.org/mbostock/3014589. On 4 December 2014 at 14:38, Maximilian Albert <max...@gm...> wrote: > Hi all, > > I had a discussion with Phil Elson about this last weekend during the > Bloomberg Open Source Day. I don't consider myself an expert on colormaps > by any means, but I started digging into them a while ago when I was > looking for a way of generating a perceptually linear *cyclic* colormap in > order to represent phase angle values. (I've been meaning to discuss this > issue on this list for a while but will do so in a different thread once I > get around to tidying up my results so far.) Phil encouraged me to reply to > this thread because he said that even non-expert views would be very > welcome, so here you go. > > Basically, I agree with most of what Nathaniel Smith suggested in his > email from November 21. I'm going to comment on some of his points inline > below and will finally suggest a way of designing a new colormap at the end. > > > Nathaniel Smith wrote: > > > it should be a sequential colormap [...] > > Agreed. > > > it should be perceptually uniform > > Agreed. > > > There's lots of research on how to measure perceptual distance -- > > a colleague and I happen to have recently implemented a > > state-of-the-art model of this for another project, in case anyone > > wants to play with it [3]. > > I haven't had time to check this out in detail yet, but it looks pretty > interesting and will certainly be very useful to assess the quality of any > suggestions. However, can this help to actually *design* a new colormap? > The answer might be hidden in the referenced paper [Luo2006], but I haven't > read it yet. > > > or just using good-old-L*a*b* is a reasonable quick-and-dirty > approximation. > > Can you elaborate how "dirty" you think using L*a*b* would be? (See my > suggestion for finding a new colormap below.) > > >- it should have a perceptually uniform luminance ramp, i.e. if you > > convert to greyscale it should still be uniform. > > Agreed. What's unclear to me is how large this luminance ramp should be. > We certainly can't go all the way to full luminance because this won't be > visible on a white background. This probably needs experimenting (again see > below). > > > - it should also have some kind of variation in hue, because > > hue variation is a really helpful additional cue to perception, > > having two cues is better than one, and there's no reason > > not to do it. > > Agreed. > > > - the hue variation should be chosen to produce reasonable results > > even for viewers with the more common types of colorblindness. > > (Which rules out things like red-to-green.) > > Agreed. Are you aware of any simple ways of avoiding the most common > issues? Are there any blog posts or papers on designing colormaps that are > suitable for colorblind people? > > > And, for bonus points, it would be nice to choose a hue ramp that > > still works if you throw away the luminance variation, because then we > > could use the version with varying luminance for 2d plots, and the > > version with just hue variation for 3d plots. (In 3d plots you really > > want to reserve the luminance channel for lighting/shading, because > > your brain is *really* good at extracting 3d shape from luminance > > variation. If the 3d surface itself has massively varying luminance > > then this screws up the ability to see shape.) > > Just out of interest, is there currently an easy way in matplotlib of > producing a 3d plot where luminance is used for lighting/shading as you > suggest? > > > Now the question is: how do we actually *design* a colormap with these > requirements? Leon Krischer's notebook [1] looks totally awesome, but if I > understand correctly the optimisation he uses "only" takes care of > linearising the luminance value, but this does not necessarily guarantee > that the hue values are also linear, right? It also feels somewhat clumsy > to me to start out with a colormap that's "wrong" (w.r.t. our requirements > above) and then "fix" it. However, the notebook looks like a great guidance > for finding suitable candidates and assessing their quality. > > It appears to me that a simple yet effective way of coming up with a good > colormap would be to pick two points in the L*a*b* color space that can be > represented by RGB values, connect them by a line and use the interpolated > values for the resulting colormap. Since L*a*b* space is (close to) > perceptually linear, this would pretty much guarantee all the requirements > above. > > What's missing is an easy way of doing this. I'm envisaging a simply GUI > which allows the user to easily pick two points in L*a*b* space, generates > a colormap from them as described above and also generates a few sample > plots to evaluate the quality of the colormap (along the lines of [1] or > the numerous blog posts linked to in the discussion). I am close to having > a prototype for such a GUI which should allow to do this relatively > painlessly. I'll try to finish it up over the weekend and will post here > once it's ready. Btw, if anyone has suggestions for sample datasets that > can help in assessing the quality of colormaps they would be much > appreciated. > > Any comments or clarifications of points that I misunderstood are very > welcome. > > Best wishes, > Max > > [1] http://nbviewer.ipython.org/gist/krischer/d35096a9d3b6da5846a5 > > > ------------------------------------------------------------------------------ > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > from Actuate! Instantly Supercharge Your Business Reports and Dashboards > with Interactivity, Sharing, Native Excel Exports, App Integration & more > Get technology previously reserved for billion-dollar corporations, FREE > > http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk > _______________________________________________ > Matplotlib-devel mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > > |
|
From: Benjamin R. <ben...@ou...> - 2014-12-21 02:17:46
|
Amit, Thanks for your bug report and your PR for fixing the bug. I haven't had time to look over it yet, and I won't have the ability to review it for the upcoming week (in fact, I will be without internet connection). If no one gets around to reviewing it in the next week due to the holiday season, then just make sure you ping us again to remind us. Cheers! Ben Root On Sat, Dec 20, 2014 at 9:02 PM, Amit Saha <ami...@gm...> wrote: > Hi all, > > I submitted a PR yesterday: > https://github.com/matplotlib/matplotlib/pull/3936 to add > autoscale_view() in the add_patch() method. This aims to fix: > https://github.com/amitsaha/matplotlib/tree/issue3934 > > I am very much a matplotlib user, so if the PR doesn't look right, I > am willing to work on it so as to fix the issue with help. > > Thanks, > Amit. > > > -- > http://echorand.me > > > ------------------------------------------------------------------------------ > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > from Actuate! Instantly Supercharge Your Business Reports and Dashboards > with Interactivity, Sharing, Native Excel Exports, App Integration & more > Get technology previously reserved for billion-dollar corporations, FREE > > http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk > _______________________________________________ > Matplotlib-devel mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > |
|
From: Amit S. <ami...@gm...> - 2014-12-21 02:03:09
|
Hi all, I submitted a PR yesterday: https://github.com/matplotlib/matplotlib/pull/3936 to add autoscale_view() in the add_patch() method. This aims to fix: https://github.com/amitsaha/matplotlib/tree/issue3934 I am very much a matplotlib user, so if the PR doesn't look right, I am willing to work on it so as to fix the issue with help. Thanks, Amit. -- http://echorand.me |
|
From: Paul H. <pmh...@gm...> - 2014-12-20 22:47:19
|
For Q and A no. But it's great for announcements, links to example of upcoming or new features, etc. — Sent from Mailbox On Sat, Dec 20, 2014 at 2:11 PM, Eric Firing <ef...@ha...> wrote: > On 2014/12/20, 10:45 AM, Thomas Caswell wrote: >> We have a Twitter account?!? > It's news to me, too. Maybe it was started by someone not closely > connected with matplotlib. I've never paid any attention to twitter, > and don't expect to in the future. If I had any control over it, I > would oppose any matplotlib presence on twitter. It's not a suitable > medium for software-related Q&A. > Eric >> >> On Fri, Dec 19, 2014, 20:05 Benjamin Root <ben...@ou... >> <mailto:ben...@ou...>> wrote: >> >> I just realized today that people have been posting questions to a >> matplotlib handle on twitter, but it hasn't posted any tweets since >> April. >> >> Same issue for numpy as well, it seems. >> >> Ben Root >> >> ------------------------------__------------------------------__------------------ >> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server >> from Actuate! Instantly Supercharge Your Business Reports and Dashboards >> with Interactivity, Sharing, Native Excel Exports, App Integration & >> more >> Get technology previously reserved for billion-dollar corporations, FREE >> http://pubads.g.doubleclick.__net/gampad/clk?id=164703151&__iu=/4140/ostg.clktrk >> <http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk>_________________________________________________ >> Matplotlib-devel mailing list >> Matplotlib-devel@lists.__sourceforge.net >> <mailto:Mat...@li...> >> https://lists.sourceforge.net/__lists/listinfo/matplotlib-__devel >> <https://lists.sourceforge.net/lists/listinfo/matplotlib-devel> >> >> >> >> ------------------------------------------------------------------------------ >> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server >> from Actuate! Instantly Supercharge Your Business Reports and Dashboards >> with Interactivity, Sharing, Native Excel Exports, App Integration & more >> Get technology previously reserved for billion-dollar corporations, FREE >> http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk >> >> >> >> _______________________________________________ >> Matplotlib-devel mailing list >> Mat...@li... >> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel >> > ------------------------------------------------------------------------------ > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > from Actuate! Instantly Supercharge Your Business Reports and Dashboards > with Interactivity, Sharing, Native Excel Exports, App Integration & more > Get technology previously reserved for billion-dollar corporations, FREE > http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk > _______________________________________________ > Matplotlib-devel mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel |
|
From: Eric F. <ef...@ha...> - 2014-12-20 22:10:38
|
On 2014/12/20, 10:45 AM, Thomas Caswell wrote: > We have a Twitter account?!? It's news to me, too. Maybe it was started by someone not closely connected with matplotlib. I've never paid any attention to twitter, and don't expect to in the future. If I had any control over it, I would oppose any matplotlib presence on twitter. It's not a suitable medium for software-related Q&A. Eric > > On Fri, Dec 19, 2014, 20:05 Benjamin Root <ben...@ou... > <mailto:ben...@ou...>> wrote: > > I just realized today that people have been posting questions to a > matplotlib handle on twitter, but it hasn't posted any tweets since > April. > > Same issue for numpy as well, it seems. > > Ben Root > > ------------------------------__------------------------------__------------------ > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > from Actuate! Instantly Supercharge Your Business Reports and Dashboards > with Interactivity, Sharing, Native Excel Exports, App Integration & > more > Get technology previously reserved for billion-dollar corporations, FREE > http://pubads.g.doubleclick.__net/gampad/clk?id=164703151&__iu=/4140/ostg.clktrk > <http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk>_________________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel@lists.__sourceforge.net > <mailto:Mat...@li...> > https://lists.sourceforge.net/__lists/listinfo/matplotlib-__devel > <https://lists.sourceforge.net/lists/listinfo/matplotlib-devel> > > > > ------------------------------------------------------------------------------ > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > from Actuate! Instantly Supercharge Your Business Reports and Dashboards > with Interactivity, Sharing, Native Excel Exports, App Integration & more > Get technology previously reserved for billion-dollar corporations, FREE > http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk > > > > _______________________________________________ > Matplotlib-devel mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > |
|
From: Thomas C. <tca...@gm...> - 2014-12-20 20:46:04
|
We have a Twitter account?!? On Fri, Dec 19, 2014, 20:05 Benjamin Root <ben...@ou...> wrote: > I just realized today that people have been posting questions to a > matplotlib handle on twitter, but it hasn't posted any tweets since April. > > Same issue for numpy as well, it seems. > > Ben Root > ------------------------------------------------------------ > ------------------ > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > from Actuate! Instantly Supercharge Your Business Reports and Dashboards > with Interactivity, Sharing, Native Excel Exports, App Integration & more > Get technology previously reserved for billion-dollar corporations, FREE > http://pubads.g.doubleclick.net/gampad/clk?id=164703151& > iu=/4140/ostg.clktrk_______________________________________________ > Matplotlib-devel mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > |
|
From: Benjamin R. <ben...@ou...> - 2014-12-20 04:04:39
|
I just realized today that people have been posting questions to a matplotlib handle on twitter, but it hasn't posted any tweets since April. Same issue for numpy as well, it seems. Ben Root |
|
From: Matthew B. <mat...@gm...> - 2014-12-12 19:33:40
|
Hi, On Tue, Oct 28, 2014 at 12:15 PM, Benjamin Root <ben...@ou...> wrote: > Yeah, put together a PR, and we can evaluate it better that way. I think the > current plot directive behavior might need this sort of tightening up Thanks for the feedback, sorry for the delay: https://github.com/matplotlib/matplotlib/pull/3916 Cheers, Matthew |
|
From: Sandro T. <mo...@de...> - 2014-12-10 20:15:28
|
great! eventually I can "use" Eric as a beta tester :) On Wed, Dec 10, 2014 at 8:11 PM, Benjamin Root <ben...@ou...> wrote: > https://github.com/matplotlib/basemap > > You can follow the same guide for matplotlib (but I suspect Jeff Whittaker > has been looser with handling it). Many of the safety checks we have in mpl > are not in basemap like the PEP8 checking, I think. > > Cheers! > Ben Root > > > On Wed, Dec 10, 2014 at 1:41 PM, Sandro Tosi <mo...@de...> wrote: >> >> hey! well, eventually in the holiday break I could give them a look, >> can you point a the bugs list? is there a devel guide for basemap in >> particular or the mpl one should be followed? >> >> Cheers, >> Sandro >> >> On Wed, Dec 10, 2014 at 6:01 PM, Benjamin Root <ben...@ou...> wrote: >> > I just noticed that the last update to basemap's master branch was March >> > 31st, but there are bug reports piling up, so people are still >> > interested in >> > at least seeing it still supported. Perhaps some of us should make a >> > concerted effort to address some of its bug reports? >> > >> > Cheers! >> > Ben Root >> > >> > >> > ------------------------------------------------------------------------------ >> > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server >> > from Actuate! Instantly Supercharge Your Business Reports and Dashboards >> > with Interactivity, Sharing, Native Excel Exports, App Integration & >> > more >> > Get technology previously reserved for billion-dollar corporations, FREE >> > >> > http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk >> > _______________________________________________ >> > Matplotlib-devel mailing list >> > Mat...@li... >> > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel >> > >> >> >> >> -- >> Sandro Tosi (aka morph, morpheus, matrixhasu) >> My website: http://matrixhasu.altervista.org/ >> Me at Debian: http://wiki.debian.org/SandroTosi > > -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi |
|
From: Benjamin R. <ben...@ou...> - 2014-12-10 20:12:10
|
https://github.com/matplotlib/basemap You can follow the same guide for matplotlib (but I suspect Jeff Whittaker has been looser with handling it). Many of the safety checks we have in mpl are not in basemap like the PEP8 checking, I think. Cheers! Ben Root On Wed, Dec 10, 2014 at 1:41 PM, Sandro Tosi <mo...@de...> wrote: > hey! well, eventually in the holiday break I could give them a look, > can you point a the bugs list? is there a devel guide for basemap in > particular or the mpl one should be followed? > > Cheers, > Sandro > > On Wed, Dec 10, 2014 at 6:01 PM, Benjamin Root <ben...@ou...> wrote: > > I just noticed that the last update to basemap's master branch was March > > 31st, but there are bug reports piling up, so people are still > interested in > > at least seeing it still supported. Perhaps some of us should make a > > concerted effort to address some of its bug reports? > > > > Cheers! > > Ben Root > > > > > ------------------------------------------------------------------------------ > > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > > from Actuate! Instantly Supercharge Your Business Reports and Dashboards > > with Interactivity, Sharing, Native Excel Exports, App Integration & more > > Get technology previously reserved for billion-dollar corporations, FREE > > > http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk > > _______________________________________________ > > Matplotlib-devel mailing list > > Mat...@li... > > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > > > > > > -- > Sandro Tosi (aka morph, morpheus, matrixhasu) > My website: http://matrixhasu.altervista.org/ > Me at Debian: http://wiki.debian.org/SandroTosi > |
|
From: Sandro T. <mo...@de...> - 2014-12-10 18:42:30
|
hey! well, eventually in the holiday break I could give them a look, can you point a the bugs list? is there a devel guide for basemap in particular or the mpl one should be followed? Cheers, Sandro On Wed, Dec 10, 2014 at 6:01 PM, Benjamin Root <ben...@ou...> wrote: > I just noticed that the last update to basemap's master branch was March > 31st, but there are bug reports piling up, so people are still interested in > at least seeing it still supported. Perhaps some of us should make a > concerted effort to address some of its bug reports? > > Cheers! > Ben Root > > ------------------------------------------------------------------------------ > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > from Actuate! Instantly Supercharge Your Business Reports and Dashboards > with Interactivity, Sharing, Native Excel Exports, App Integration & more > Get technology previously reserved for billion-dollar corporations, FREE > http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk > _______________________________________________ > Matplotlib-devel mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi |
|
From: Eric F. <ef...@ha...> - 2014-12-10 18:40:59
|
On 2014/12/10, 8:01 AM, Benjamin Root wrote: > I just noticed that the last update to basemap's master branch was March > 31st, but there are bug reports piling up, so people are still > interested in at least seeing it still supported. Perhaps some of us > should make a concerted effort to address some of its bug reports? > > Cheers! > Ben Root Good idea, thanks for pointing this out. I rely on it heavily, and expect to continue to do so for a long time. Unfortunately, I don't expect to have much (any?) time to work on it. Eric |
|
From: Benjamin R. <ben...@ou...> - 2014-12-10 18:01:27
|
I just noticed that the last update to basemap's master branch was March 31st, but there are bug reports piling up, so people are still interested in at least seeing it still supported. Perhaps some of us should make a concerted effort to address some of its bug reports? Cheers! Ben Root |
|
From: Matthew A. <mat...@ya...> - 2014-12-08 15:40:34
|
Hi Benjamin and others: Thx for your comments. I've tried to follow your recommendations and simplify the code:http://pastebin.com/JHhkcCzt Prior to these modifications I would at least see my axes render on the gridLayout object, but now that doesn't populate. Here's my attempt to talk through what I think is happening:LINE 9: I import the FigureCanvasQTAgg class. A figureCanvas is an object on which we can attach figures, and subsequently axes and plots. I guess since I want to embed this figureCanvas into a pyqt4 GUI, I'm importing a special type of figureCanvas from the backend_qtAgg library to do this?? Not sure if that's the case. LINE 24: I want to create a FigureCanvas object called thePlot on which I will create a simple line plot. It seems that in order to instantiate this new object, I need to pass a Figure object so I use LINE 24 to do that. LINE 25: In this line I create a a FigureCanvas object called thePlot and pass the Figure I created in LINE 24. LINE 26: My objective is to attached this plot to a pyqt4 GUI. I've created a gridLayout on the GUI. In this line I execute the addWidget method and pass thePlot object as argument. A FigureCanvas is a QWidget apparently which makes this a reasonable thing to do I guess.... LINE 119: I'm now in the pushbutton signal function. This line sets the parent of thePlot to None. I have no idea what this does. This is just something I put in there because I hoped it would help make things work. Adding it didn't help. LINE 120: Here I set the variable self.axes equal to the return of the fig function add_subplot. This is something I just copied from an example. I understand that add_subplot(111) creates one row and column of figures and selects the first one(from matlab), but I'm not really grasping what's really going on here. I've followed the declaration of add_subplot and find that the function is return something called a subplot_class_factory. I don't really know what this is either so I followed this declaration too. I find that a subplot_class_factory is a function that creates a new class that inherits from SubplotBase. Again I'm not sure what a subplotbase is and decide to just accept the original statement and hope it works. Is looking at the declarations a reasonable way to figure out how things work in matplotlib? I don't know a better strategy. For somebody with so little experience, it's been very difficult to gain much benefit from. Line 122: Lastly I attempt to plot. I saw in an example that the .plot method is available from a subplotbase. Here I try something very simple, just three numbers. THE OUTCOME: The axes never rendered and the plot never appeared. I really don't know why or how to troubleshoot this. Does anybody have an idea why? thxMatt On Friday, December 5, 2014 4:29 PM, Benjamin Root <ben...@ou...> wrote: I would look at line 24/25. You are constructing a MyStaticMplCanvas instance on 24, with a self.main_widget as the parent. But then on 25, you explicitly call the constructor again (which is not a good idea), but with the main window as the parent (the self argument). I bet that is throwing off a couple things. The code is extremely hard to follow, and I think it is a bad example to build off of in the first place (unnescessary subclassing). Perhaps a different example would be more suitable? What programming language are you coming from? Ben Root On Fri, Dec 5, 2014 at 4:12 PM, Matthew Albert <mat...@ya...> wrote: I'm sure this is a simple problem, but I've been going around in circles several days trying to figure this out. Here's my code.http://pastebin.com/n83dGhG4 Basically, I'm trying to get my pyqt4 button signal to execute the plot command (line 122). A lot of this code was copied from the matplotlib example page. If I uncomment line 148, the figure will successfully plot. I don't understand why what I'm doing on line 122 isn't equivalent to line 148. thx for your help.Matt ------------------------------------------------------------------------------ Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server from Actuate! Instantly Supercharge Your Business Reports and Dashboards with Interactivity, Sharing, Native Excel Exports, App Integration & more Get technology previously reserved for billion-dollar corporations, FREE http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk _______________________________________________ Matplotlib-devel mailing list Mat...@li... https://lists.sourceforge.net/lists/listinfo/matplotlib-devel |
|
From: Hubert H. <Hub...@fr...> - 2014-12-07 23:58:26
|
Paris (U.E.), le 08/12/2014 The transition to MacOS X 10.10 (and more precisely 10.10.1) is proving quite problematic. One problem I am currently stuck with prevents me from using matplotlib. Whether using matplotlib 1.4.2 and freetype 2.3.12 (combination A) or matplotlib 59eda228e6a77e842c63078c3af870868120e70c and freetype 2.5.3 (combination B), importing matplotlib.pylab results in a crash. I have not tried other combinations… In the case of combination A, the crash occurs because FT_Set_Char_Size (ft2font.cpp, line 909) returns an error because of the font “/System/Library/Fonts/Apple Color Emoji.ttf” and an uncaught exception is then thrown on line 916. In the case of combination B, the crash occurs because FT_Set_Char_Size (ft2font.cpp, line 508) returns an error because of an unidentified font (I could not quickly find a way, in this version of the file, to access the name of the font being tested…) and an uncaught exception is then thrown on line 510. As the font “/System/Library/Fonts/Apple Color Emoji.ttf” is a system font, and therefore off-limits to most users, it would be unadvisable to mess with it (including removing it from the system), and even though I would personally be quite unlikely to use it in conjunction with matplotlib, our Japanese colleagues might see things differently. At any rate, it does not seem to be corrupt (it may be complex, though, as TypeTool displays it differently from Font Book, which is hardly surprising as it is a *color* font…). Barring a more sophisticated treatment of such fonts, could it be possible to catch the exception, just not take these fonts into account, and move on to the rest of the work? I have not grasped the organisation of the source that well to know where to propose a patch. Any hint welcome! Hubert Holin P.S.: I have also not found a way of creating a figure without having to import matplotlib.pylab. |
|
From: Benjamin R. <ben...@ou...> - 2014-12-05 21:29:25
|
I would look at line 24/25. You are constructing a MyStaticMplCanvas instance on 24, with a self.main_widget as the parent. But then on 25, you explicitly call the constructor again (which is not a good idea), but with the main window as the parent (the self argument). I bet that is throwing off a couple things. The code is extremely hard to follow, and I think it is a bad example to build off of in the first place (unnescessary subclassing). Perhaps a different example would be more suitable? What programming language are you coming from? Ben Root On Fri, Dec 5, 2014 at 4:12 PM, Matthew Albert <mat...@ya...> wrote: > I'm sure this is a simple problem, but I've been going around in circles > several days trying to figure this out. > > Here's my code. > http://pastebin.com/n83dGhG4 > > Basically, I'm trying to get my pyqt4 button signal to execute the plot > command (line 122). A lot of this code was copied from the matplotlib > example page. If I uncomment line 148, the figure will successfully plot. > I don't understand why what I'm doing on line 122 isn't equivalent to line > 148. > > thx for your help. > Matt > > > ------------------------------------------------------------------------------ > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > from Actuate! Instantly Supercharge Your Business Reports and Dashboards > with Interactivity, Sharing, Native Excel Exports, App Integration & more > Get technology previously reserved for billion-dollar corporations, FREE > > http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk > _______________________________________________ > Matplotlib-devel mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > > |
|
From: Matthew A. <mat...@ya...> - 2014-12-05 21:12:09
|
I'm sure this is a simple problem, but I've been going around in circles several days trying to figure this out. Here's my code.http://pastebin.com/n83dGhG4 Basically, I'm trying to get my pyqt4 button signal to execute the plot command (line 122). A lot of this code was copied from the matplotlib example page. If I uncomment line 148, the figure will successfully plot. I don't understand why what I'm doing on line 122 isn't equivalent to line 148. thx for your help.Matt |
|
From: Maximilian A. <max...@gm...> - 2014-12-04 14:38:08
|
Hi all, I had a discussion with Phil Elson about this last weekend during the Bloomberg Open Source Day. I don't consider myself an expert on colormaps by any means, but I started digging into them a while ago when I was looking for a way of generating a perceptually linear *cyclic* colormap in order to represent phase angle values. (I've been meaning to discuss this issue on this list for a while but will do so in a different thread once I get around to tidying up my results so far.) Phil encouraged me to reply to this thread because he said that even non-expert views would be very welcome, so here you go. Basically, I agree with most of what Nathaniel Smith suggested in his email from November 21. I'm going to comment on some of his points inline below and will finally suggest a way of designing a new colormap at the end. Nathaniel Smith wrote: > it should be a sequential colormap [...] Agreed. > it should be perceptually uniform Agreed. > There's lots of research on how to measure perceptual distance -- > a colleague and I happen to have recently implemented a > state-of-the-art model of this for another project, in case anyone > wants to play with it [3]. I haven't had time to check this out in detail yet, but it looks pretty interesting and will certainly be very useful to assess the quality of any suggestions. However, can this help to actually *design* a new colormap? The answer might be hidden in the referenced paper [Luo2006], but I haven't read it yet. > or just using good-old-L*a*b* is a reasonable quick-and-dirty approximation. Can you elaborate how "dirty" you think using L*a*b* would be? (See my suggestion for finding a new colormap below.) >- it should have a perceptually uniform luminance ramp, i.e. if you > convert to greyscale it should still be uniform. Agreed. What's unclear to me is how large this luminance ramp should be. We certainly can't go all the way to full luminance because this won't be visible on a white background. This probably needs experimenting (again see below). > - it should also have some kind of variation in hue, because > hue variation is a really helpful additional cue to perception, > having two cues is better than one, and there's no reason > not to do it. Agreed. > - the hue variation should be chosen to produce reasonable results > even for viewers with the more common types of colorblindness. > (Which rules out things like red-to-green.) Agreed. Are you aware of any simple ways of avoiding the most common issues? Are there any blog posts or papers on designing colormaps that are suitable for colorblind people? > And, for bonus points, it would be nice to choose a hue ramp that > still works if you throw away the luminance variation, because then we > could use the version with varying luminance for 2d plots, and the > version with just hue variation for 3d plots. (In 3d plots you really > want to reserve the luminance channel for lighting/shading, because > your brain is *really* good at extracting 3d shape from luminance > variation. If the 3d surface itself has massively varying luminance > then this screws up the ability to see shape.) Just out of interest, is there currently an easy way in matplotlib of producing a 3d plot where luminance is used for lighting/shading as you suggest? Now the question is: how do we actually *design* a colormap with these requirements? Leon Krischer's notebook [1] looks totally awesome, but if I understand correctly the optimisation he uses "only" takes care of linearising the luminance value, but this does not necessarily guarantee that the hue values are also linear, right? It also feels somewhat clumsy to me to start out with a colormap that's "wrong" (w.r.t. our requirements above) and then "fix" it. However, the notebook looks like a great guidance for finding suitable candidates and assessing their quality. It appears to me that a simple yet effective way of coming up with a good colormap would be to pick two points in the L*a*b* color space that can be represented by RGB values, connect them by a line and use the interpolated values for the resulting colormap. Since L*a*b* space is (close to) perceptually linear, this would pretty much guarantee all the requirements above. What's missing is an easy way of doing this. I'm envisaging a simply GUI which allows the user to easily pick two points in L*a*b* space, generates a colormap from them as described above and also generates a few sample plots to evaluate the quality of the colormap (along the lines of [1] or the numerous blog posts linked to in the discussion). I am close to having a prototype for such a GUI which should allow to do this relatively painlessly. I'll try to finish it up over the weekend and will post here once it's ready. Btw, if anyone has suggestions for sample datasets that can help in assessing the quality of colormaps they would be much appreciated. Any comments or clarifications of points that I misunderstood are very welcome. Best wishes, Max [1] http://nbviewer.ipython.org/gist/krischer/d35096a9d3b6da5846a5 |
|
From: Benjamin R. <ben...@ou...> - 2014-12-02 22:13:12
|
I think line 102 is your problem. self.axes doesn't exist yet. Ben Root P.S. - <shameless_plug>stuff like this will be covered in my upcoming book. I am wrapping up with the embedding chapter tonight, even! Stay tuned for announcements in the coming weeks.</shameless_plug> On Tue, Dec 2, 2014 at 5:00 PM, Matthew Albert <mat...@ya...> wrote: > Hi, > > I've used Qt Designer to construct a GUI. An element of the GUI is a > QGridLayout. I've been trying to display a matplotlib plot in this > QGridLayout. I'm new at Python and have been trying to figure this out for > the last week without success. Essentially I'm trying to use elements of > the example shown here: > user_interfaces example code: embedding_in_qt4.py — Matplotlib 1.4.2 > documentation > <http://matplotlib.org/examples/user_interfaces/embedding_in_qt4.html> > > in my code shown here: > http://paste.ofcode.org/JA2Hm8cP4jYD4c9NXgVGaE > > Lines 23-25 is the problem area. The error I get now is: > RuntimeError: super-class __init__() of type MyStaticMplCanvas was never > called > > Conceptually what I think I'm doing is: > # Line 24 Create an object of type MyStaticMplCanvas called thePlot. > This object is essentially a QWidget. > thePlot = MyStaticMplCanvas(self.main_widget) > > # Line 25 Pass thePlot as an argument to the addWidget method of the > gridLayout I created in Qt Designer. > self.ui.gridLayout.addWidget(thePlot) > > Thx for the help. I've spent about twenty hour trying to figure out this > myself. Any help you can give me would be great! > > Matt > > > > > ------------------------------------------------------------------------------ > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > from Actuate! Instantly Supercharge Your Business Reports and Dashboards > with Interactivity, Sharing, Native Excel Exports, App Integration & more > Get technology previously reserved for billion-dollar corporations, FREE > > http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk > _______________________________________________ > Matplotlib-devel mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > > |
|
From: Matthew A. <mat...@ya...> - 2014-12-02 22:00:24
|
Hi, I've used Qt Designer to construct a GUI. An element of the GUI is a QGridLayout. I've been trying to display a matplotlib plot in this QGridLayout. I'm new at Python and have been trying to figure this out for the last week without success. Essentially I'm trying to use elements of the example shown here:user_interfaces example code: embedding_in_qt4.py — Matplotlib 1.4.2 documentation in my code shown here:http://paste.ofcode.org/JA2Hm8cP4jYD4c9NXgVGaE Lines 23-25 is the problem area. The error I get now is:RuntimeError: super-class __init__() of type MyStaticMplCanvas was never called Conceptually what I think I'm doing is:# Line 24 Create an object of type MyStaticMplCanvas called thePlot. This object is essentially a QWidget.thePlot = MyStaticMplCanvas(self.main_widget) # Line 25 Pass thePlot as an argument to the addWidget method of the gridLayout I created in Qt Designer.self.ui.gridLayout.addWidget(thePlot) Thx for the help. I've spent about twenty hour trying to figure out this myself. Any help you can give me would be great! Matt |
|
From: Nathaniel S. <nj...@po...> - 2014-11-28 00:50:30
|
On Thu, Nov 27, 2014 at 9:54 AM, Todd <tod...@gm...> wrote:
>
> On Nov 26, 2014 10:04 PM, "Nathaniel Smith" <nj...@po...> wrote:
>>
>> The main differences in requirements are:
>> - for the color cycle, you want isoluminant colors, to avoid the issue
>> where one line is glaring bright red and one is barely-visible-grey.
>> For general-purpose 2d colormaps, though, you almost always want the
>> luminance to vary to help distinguish colors from each other.
>
> If you used isoluminance colors for the lines, wouldn't that mean a plot
> printed in grayscale would have all lines be the same shade of gray?
Yes. But IME it's very difficult to use greyscale alone to distinguish
between multiple plot lines no matter what: you can't go much beyond 2
lines before you either end up with hard-to-see lines (b/c they don't
have enough contrast with the white background) or the lines become
nigh-indistinguishable ("which one is the slightly-darker grey?"). And
if you have substantial luminance variation to make the greyscale
work, then the color images end up looking really weird (the scarlet
versus faint-yellow problem, where you end up emphasizing one set of
data over another -- emphasis should be done on purpose! in
matplotlib's current color cycle the yellow and cyan tend to
disappear).
If you're worried about greyscale then IMHO you should use different
line styles (solid/dashed/dotted/...) and/or use solid black for
everything and label the lines directly.
Which isn't to say that there's never any value in picking line colors
from a colormap, it's just more complicated than it seems :-).
-n
--
Nathaniel J. Smith
Postdoctoral researcher - Informatics - University of Edinburgh
http://vorpus.org
|
|
From: Thomas C. <tca...@gm...> - 2014-11-27 20:02:16
|
For reference, the IPython script is in tools/update_whatsnew.py On Thu Nov 27 2014 at 11:58:40 AM Ian Thomas <ian...@gm...> wrote: > On 27 November 2014 at 16:16, Thomas Caswell <tca...@gm...> wrote: > >> There should be an automatic process, but no one has written it yet. I >> think IPython has code we can adapt in their doc build process. I had >> planned to deal with this when we cut the next minor/major release. >> >> Tom >> > > Thanks for letting me know Tom. > > Ian > |
|
From: Ian T. <ian...@gm...> - 2014-11-27 16:58:46
|
On 27 November 2014 at 16:16, Thomas Caswell <tca...@gm...> wrote: > There should be an automatic process, but no one has written it yet. I > think IPython has code we can adapt in their doc build process. I had > planned to deal with this when we cut the next minor/major release. > > Tom > Thanks for letting me know Tom. Ian |
|
From: Thomas C. <tca...@gm...> - 2014-11-27 16:16:32
|
There should be an automatic process, but no one has written it yet. I think IPython has code we can adapt in their doc build process. I had planned to deal with this when we cut the next minor/major release. Tom On Thu, Nov 27, 2014, 04:18 Ian Thomas <ian...@gm...> wrote: > Fellow developers, > > I know we are now encouraged when writing a PR not to alter > doc/users/whats_new.rst and doc/api/api_changes.rst directly, but rather to > create files in the doc/users/whats_new and doc/api/api_changes directories > instead. When building the master branch docs I was expecting the contents > of these new files to be automagically incorporated in the appropriate doc > sections, but this does not happen on my development system (ubuntu 14.04, > python 2.7, sphinx 1.2.2). > > I figure either I am doing something wrong, or this is a bug, or there is > manual process at release time to cut and paste the new files into the > parent files. Which is it? > > Ian > ------------------------------------------------------------ > ------------------ > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > from Actuate! Instantly Supercharge Your Business Reports and Dashboards > with Interactivity, Sharing, Native Excel Exports, App Integration & more > Get technology previously reserved for billion-dollar corporations, FREE > http://pubads.g.doubleclick.net/gampad/clk?id=157005751& > iu=/4140/ostg.clktrk_______________________________________________ > Matplotlib-devel mailing list > Mat...@li... > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel > |
|
From: Todd <tod...@gm...> - 2014-11-27 09:54:51
|
On Nov 26, 2014 10:04 PM, "Nathaniel Smith" <nj...@po...> wrote: > > On Wed, Nov 26, 2014 at 9:30 AM, Todd <tod...@gm...> wrote: > > On Sat, Nov 22, 2014 at 12:22 AM, Nathaniel Smith <nj...@po...> wrote: > >> > >> - Default line colors: The rgbcmyk color cycle for line plots doesn't > >> appear to be based on any real theory about visualization -- it's just > >> the corners of the RGB color cube, which is a highly perceptually > >> non-uniform space. The resulting lines aren't terribly high contrast > >> against the default white background, and the different colors have > >> varying luminance that makes some lines "pop out" more than others. > >> > >> Seaborn's default is to use a nice isoluminant variant on matplotlib's > >> default: > >> > >> http://web.stanford.edu/~mwaskom/software/seaborn/tutorial/aesthetics.html > >> ggplot2 uses isoluminant colors with maximally-separated hues, which > >> also works well. E.g.: > >> > >> http://www.cookbook-r.com/Graphs/Colors_%28ggplot2%29/ggplot2_scale_hue_colors_l45.png > > > > About this, I am not expert so forgive me if this is nonsensical. However, > > it would seem to me that these requirements are basically the same as the > > requirements for the new default colormap that prompted this whole > > discussion. So, rather than create two inconsistent set of colors that > > accomplish similar goals, might it be better to instead use the default > > colormap for the line colors? You could pick "N" equally-spaced colors from > > the colormap and use those as the line colors. > > The main differences in requirements are: > - for the color cycle, you want isoluminant colors, to avoid the issue > where one line is glaring bright red and one is barely-visible-grey. > For general-purpose 2d colormaps, though, you almost always want the > luminance to vary to help distinguish colors from each other. If you used isoluminance colors for the lines, wouldn't that mean a plot printed in grayscale would have all lines be the same shade of gray? |
127 messages has been excluded from this view by a project administrator.
