Mailman 3 August 2015 - Matplotlib-devel

Fwd: patch for stream prediction in pdf backend
by Cornelius Weig Sept. 13, 2015

Sept. 13, 2015

Hi, I have implemented PNG stream prediction for the pdf backend. It was marked as a TODO. Cheers, Cornelius ------------------- Details: At first I thought about linking to libpng, but I couldn't find an API for raw encoding of single lines as PDF needs it. Therefore, I implemented the code in plain python (it makes heavy use of numpy to do the number crunching). It needs testing with python 3 however... I took care of five different encoding modes as specified by RFC 2083: 10 - noop 11 - Sub encoding 12 - Up encoding 13 - Avg encoding 14 - Paeth encoding 15 - Optimal encoding (*) (*) For '15', I considered only modes 10-13, because my Paeth implementation is not very fast (nor very clean). The prediction is done by a static method in the 'Stream' class, which is called from writeImages. My heuristics have shown (and http://www.libpng.org/pub/png/book/chapter09.html also mentions it) that gray-scale data does usually not benefit from stream prediction. Therefore, the prediction is only applied to color images. Finally, I think that the encoding mode is something to be made adjustable by the user, so that a rcParams['pdf.prediction'] (or 'filter' or 'pngcompression') setting should be justified. I didn't touch anything of this, because that's up to you devs.

3 2

Re: [Matplotlib-devel] [matplotlib-devel] matplotlib 1.5.1 closed path in draw_path when it is not necessary closed
by Thomas Caswell Sept. 12, 2015

Sept. 12, 2015

Please keep all discussion on the mailing list (matplotlib-devel(a)python.org ). Being pedantic about versions, current master is v1.5.0dev1 , not 1.5.1 (which will be the first bug fix release in the 1.5 series which may or may not ever happen). I don't have gtk installed to easily test this and it looks fine with qt4agg, can you provide a minimal script and the code paths from a simple polygon? Tom On Fri, Aug 14, 2015 at 9:05 AM Andrés Vargas <andnovar(a)gmail.com> wrote: > Hello Tom, > > Thanks for your prompt reply. I am using the function path.to_polygons() > and that gives me a non-closed path in matplotlib 1.4.3 (last stable > release) and give me a closed path in 1.5.1 (master from github). You can > see the problem if you run integral_demo.py with matplotlib 1.5.1 master > with matplotlib.use('gtk'). > > Thanks, Andres > > On Fri, Aug 14, 2015 at 8:13 AM, Thomas Caswell <tcaswell(a)gmail.com> > wrote: > >> Did you mean 1.4.1 instead of 1.5.1 ? >> >> Exactly which paths are you looking at and how are you generating then on >> the mpl side? We have many ways to generate the paths and there maybe >> inconsistence in how closed paths are handled. >> >> Tom >> >> On Wed, Aug 12, 2015, 1:57 PM Andrés Vargas <andnovar(a)gmail.com> wrote: >> >>> Hello, >>> >>> My name is Andres I am developing a backend for kivy. I was initially >>> developing for 1.5.1 and I found that the paths are coming with the initial >>> vertex at the end of the list. Does anyone know whether this is change in >>> the way paths are sent ? and how can be fixed coming from 1.4.3 since I am >>> developing the backend for that version. >>> >>> Thanks, Andres >>> >>> ------------------------------------------------------------------------------ >>> _______________________________________________ >>> Matplotlib-devel mailing list >>> Matplotlib-devel(a)lists.sourceforge.net >>> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel >>> >> > > >

3 7

Re: [Matplotlib-devel] [matplotlib-devel] IMPORTANT: Mailing lists are moving
by Nicolas P. Rougier Sept. 9, 2015

Sept. 9, 2015

The mailing list pointer on the first page on matplotlib.org stil point to old mailing lists. See: Check the faq, the api docs, mailing list archives, and join the matplotlib mailing lists. Check out the matplotlib questions on stackoverflow. The search tool searches all of the documentation, including full text search of over 350 complete examples which exercise almost every corner of matplotlib. Nicolas > On 31 Jul 2015, at 19:07, Michael Droettboom <mdroe(a)stsci.edu> wrote: > > Due to recent technical problems and changes in policy on SourceForge, we have decided to move the matplotlib mailing lists to python.org. > > To subscribe to the new mailing lists, please visit: > > • For user questions and support: > https://mail.python.org/mailman/listinfo/matplotlib-users > matplotlib-users(a)python.org > • For low-volume announcements about matplotlib releases and related events and software: > https://mail.python.org/mailman/listinfo/matplotlib-announce > matplotlib-announce(a)python.org > • For developer discussion: > https://mail.python.org/mailman/listinfo/matplotlib-devel > matplotlib-devel(a)python.org > The old list will remain active in the meantime, but all new posts will auto-reply with the location of the new mailing lists. > > The old mailing list archives will remain available. > > Thanks to Ralf Hildebrandt at python.org for making this possible. > > Cheers, > Michael Droettboom > > ------------------------------------------------------------------------------ > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

2 2

Re: [Matplotlib-devel] [matplotlib-devel] Running test suite with out image comparisons
by Thomas Caswell Aug. 31, 2015

Aug. 31, 2015

Not that I know of, but that seems like a useful thing to have. All of the image tests use the `@image_comparison` decorator, we could check something in there an raise SkipTest. Tom On Tue, Jul 21, 2015 at 9:11 PM Brian Granger <ellisonbg(a)gmail.com> wrote: > Hi folks, > > Is it possible to run the matplotlib test suite without the image > comparisons? > > Cheers, > > Brian > > -- > Brian E. Granger > Cal Poly State University, San Luis Obispo > @ellisonbg on Twitter and GitHub > bgranger(a)calpoly.edu and ellisonbg(a)gmail.com > > > ------------------------------------------------------------------------------ > Don't Limit Your Business. Reach for the Cloud. > GigeNET's Cloud Solutions provide you with the tools and support that > you need to offload your IT needs and focus on growing your business. > Configured For All Businesses. Start Your Cloud Today. > https://www.gigenetcloud.com/ > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel >

2 1

Re: [Matplotlib-devel] [matplotlib-devel] Alternative way of specifying plot layout
by Thomas Caswell Aug. 31, 2015

Aug. 31, 2015

We are starting to wrap up 1.5 (finally), getting this rolling again would be great! Tom On Sun, Apr 26, 2015 at 1:52 PM Thomas Caswell <tcaswell(a)gmail.com> wrote: > I am in favor of doing in in PR comments so we can to line comments. > > On Sun, Apr 26, 2015 at 3:47 AM Nicolas P. Rougier < > Nicolas.Rougier(a)inria.fr> wrote: > >> >> Great ! Thanks for setting this up. One comment, it would be great to >> have a README.rst in the directory to have abstract of all MEPS at once in >> github (I can make a PR). >> >> >> I've started working on MEP28 ( >> https://github.com/rougier/matplotlib/blob/MEP28/doc/devel/MEP/MEP28.rst). >> I intend to make a PR once it is a bit more polished or should I make a PR >> right now to initiate the discussion on the PR ? (It is not clear to me if >> the preferred medium for discussion is the mailing list or the PR comments). >> >> >> Nicolas >> >> > On 25 Apr 2015, at 23:04, Thomas Caswell <tcaswell(a)gmail.com> wrote: >> > >> > The MEP tree has been moved into the main repo >> https://github.com/matplotlib/matplotlib/tree/master/doc/devel/MEP >> > >> > I am pretty excited about this feature. >> > >> > I don't remember if this got mentioned upthread, but this ties in with >> https://github.com/matplotlib/matplotlib/issues/1109 as a nice way to >> set up all of the constraints. >> > >> > Tom >> > >> > On Thu, Mar 19, 2015 at 1:10 PM Nicolas P. Rougier < >> Nicolas.Rougier(a)inria.fr> wrote: >> > Ok. I'll wait for the MEP directory to start writing a proposal. >> > Here is a flavor of what I think could be done (to be seen using a >> fixed width font): >> > >> > >> > "AB": >> > ┌────────┐┌────────┐ >> > │ A ││ B │ >> > │ ││ │ >> > │ ││ │ >> > └────────┘└────────┘ >> > >> > "ABB": >> > ┌──────┐┌──────────┐ >> > │ A ││ B │ >> > │ ││ │ >> > │ ││ │ >> > └──────┘└──────────┘ >> > >> > "ABD" >> > "CCD": >> > ┌───────┐┌───────┐┌───────┐ >> > │ A ││ B ││ D │ >> > │ ││ ││ │ >> > │ ││ ││ │ >> > └───────┘└───────┘│ │ >> > ┌────────────────┐│ │ >> > │ C ││ │ >> > │ ││ │ >> > └────────────────┘└───────┘ >> > >> > "AaBb": >> > ┌───────┐┌─┐┌───────┐┌─┐ >> > │ A ││ ││ B ││ │ >> > │ ││ ││ ││ │ >> > │ ││ ││ ││ │ >> > └───────┘└─┘└───────┘└─┘ >> > >> > " b " >> > "aABCc": >> > ┌───────┐ >> > └───────┘ >> > ┌─┐┌───────┐┌───────┐┌───────┐┌─┐ >> > │ ││ A ││ B ││ C ││ │ >> > │ ││ ││ ││ ││ │ >> > │ ││ ││ ││ ││ │ >> > └─┘└───────┘└───────┘└───────┘└─┘ >> > >> > >> > >> > >> >> On 19 Mar 2015, at 15:34, Benjamin Root <ben.root(a)ou.edu> wrote: >> >> >> >> two problems with that: 1) that really doesn't make me want to use >> this approach, especially since I wouldn't know what ratios I would want in >> the first place. 2) it can't tell if I want a horizontal or vertical >> colorbar, whereas the lower-case notation could have some logic to >> auto-detect the user's intent (e.g., all lower-case letters in the last row >> indicates horizontal bars). It would also allow us to return the plotting >> axes separate from the colorbar axes, which is how axes_grid1 does it, and >> it is very nice that way. >> >> >> >> On Thu, Mar 19, 2015 at 6:31 AM, Nicolas P. Rougier < >> Nicolas.Rougier(a)inria.fr> wrote: >> >> >> >> I think you could specify colorbars using: ["AAAAAAAAAB"] >> >> (B is a vertical colorbar, 1/10 of total width) >> >> >> >> Nicolas >> >> >> >> >> >> >> >> > On 18 Mar 2015, at 18:52, Eric Firing <efiring(a)hawaii.edu> wrote: >> >> > >> >> > On 2015/03/18 7:42 AM, Benjamin Root wrote: >> >> >> A thought... could this perhaps be extended somehow to specify >> colorbars >> >> >> in the layout? >> >> > >> >> > A lower-case letter could indicate a colorbar-size Axes: >> >> > >> >> > layout = ["ABc", >> >> > "DE ", >> >> > "ff "] >> >> > >> >> > would put a vertical think axes to the right of B, and a double-wide >> >> > hoizontal one below D and E. >> >> > >> >> > All of this seems like an alternative API for gridspec and >> axes_grid1. >> >> > >> >> > I am concerned about ending up with too many ways to do things, but >> with >> >> > subtle differences. >> >> > >> >> > How much control over spacing and sizing would be provided by kwargs >> or >> >> > other adjustment mechanisms? How would this relate to >> subplot_params? >> >> > >> >> > Eric >> >> > >> >> > >> >> > >> >> > >> ------------------------------------------------------------------------------ >> >> > Dive into the World of Parallel Programming The Go Parallel Website, >> sponsored >> >> > by Intel and developed in partnership with Slashdot Media, is your >> hub for all >> >> > things parallel software development, from weekly thought leadership >> blogs to >> >> > news, videos, case studies, tutorials and more. Take a look and join >> the >> >> > conversation now. http://goparallel.sourceforge.net/ >> >> > _______________________________________________ >> >> > Matplotlib-devel mailing list >> >> > Matplotlib-devel(a)lists.sourceforge.net >> >> > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel >> >> >> >> >> >> >> ------------------------------------------------------------------------------ >> >> Dive into the World of Parallel Programming The Go Parallel Website, >> sponsored >> >> by Intel and developed in partnership with Slashdot Media, is your hub >> for all >> >> things parallel software development, from weekly thought leadership >> blogs to >> >> news, videos, case studies, tutorials and more. Take a look and join >> the >> >> conversation now. http://goparallel.sourceforge.net/ >> >> _______________________________________________ >> >> Matplotlib-devel mailing list >> >> Matplotlib-devel(a)lists.sourceforge.net >> >> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel >> >> >> > >> > >> ------------------------------------------------------------------------------ >> > Dive into the World of Parallel Programming The Go Parallel Website, >> sponsored >> > by Intel and developed in partnership with Slashdot Media, is your hub >> for all >> > things parallel software development, from weekly thought leadership >> blogs to >> > news, videos, case studies, tutorials and more. Take a look and join the >> > conversation now. >> http://goparallel.sourceforge.net/_________________________________________… >> > Matplotlib-devel mailing list >> > Matplotlib-devel(a)lists.sourceforge.net >> > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel >> >>

1 0

Re: [Matplotlib-devel] [matplotlib-devel] Travis build of development matplotlib?
by Thomas Caswell Aug. 30, 2015

Aug. 30, 2015

I do not know of anyone who is building conda packages off of master regularly. Phil Elson has been working on continuous deployment tools, but none of that is set up on matplotlib yet. One (possibly) easy path to getting this add a hook into our .travis.yml file that pokes binstar/anaconda.org to build the linux binaries whenever master passes (we are using the same hook to deploy the devdocs ( matplotlib.org/devdocs). I think all that needs to be done for that is for mpl to include a working conda recipe and the right yaml file. Tom PS: the dev list has moved to matplotlib-devel(a)python.org On Sat, Aug 29, 2015, 3:27 PM Michael Waskom <mwaskom(a)stanford.edu> wrote: > Hi all, > > I would like to set up a Travis build of seaborn that tests against the > development version of matplotlib. Ideally this would happen without > actually compiling matplotlib on Travis, to save time. > > Does matplotlib master get packaged such that it is installable through > conda? I thought I recalled seeing this somewhere, but I am having trouble > digging it up. > > Thanks! > Michael > > ------------------------------------------------------------------------------ > _______________________________________________ > Matplotlib-devel mailing list > Matplotlib-devel(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel >

1 0

When panning text gets out of bounds
by Andrés Vargas Aug. 21, 2015

Aug. 21, 2015

Hello, I am writing to let you know guys that while implementing a backend I run into an issue when doing panning. Which render the texts outside the axes. I tried to solve it but I had no way to know if the text is either from inside the axes or outside. I think this perhaps need a change in backend_bases. I looked into the other backends and they have the same problem even GtkCairo. http://imagebin.ca/v/2Coe4Nzw3hZl The problem can be seen on there with the text inside the axes. Thanks, Andres

2 2

Issue when zooming
by Andrés Vargas Aug. 21, 2015

Aug. 21, 2015

Hello, I came up with this issue while implementing the kivy backend, the problem is explained in the comments of this issue, but basically according to the debugging I did, draw_path receives just the paths that are visible so when zooming for instance on an edge of a bar the number of vertices is not enough to construct a polygon. https://github.com/andnovar/kivy/issues/72 Thanks, Andres

1 0

v1.5 update
by Thomas Caswell Aug. 14, 2015

Aug. 14, 2015

Hey all, An update on where we stand in the next release given that the RC is 2 weeks late. At this point I don't think we have a target date, just when ever this all gets done. A long list of regressions was reported by James Evans ( https://github.com/matplotlib/matplotlib/issues/4897) all of which should probably be blockers, but most of them have too little detail to easily tell. James is working on getting PRs in for them. Many of the gui related issues are due to a change in Qt5 that produces too many mouse events on mouse motion. nbagg There needs to be a bit more work done on sorting out how closing figures works - https://github.com/matplotlib/matplotlib/issues/4841 - https://github.com/matplotlib/matplotlib/pull/4456 There are a few major feature PRs outstanding: - https://github.com/matplotlib/matplotlib/pull/4829 (I think this is converging, needs review) - https://github.com/matplotlib/matplotlib/pull/4686 (use cycler internally, still needs work) - https://github.com/matplotlib/matplotlib/pull/4666 (piecewise linear norm, still needs work) - https://github.com/matplotlib/matplotlib/pull/4488 (enusure_ax decorators in pyplot, ready to go) - https://github.com/matplotlib/matplotlib/pull/3937 (improved rectangle selector widgets, ready to go modulo example updates) Stale / auto redraw related - https://github.com/matplotlib/matplotlib/issues/4732 - (PR) https://github.com/matplotlib/matplotlib/pull/4738 (This should be ready for final review) Performance regressions - https://github.com/matplotlib/matplotlib/issues/4918 - https://github.com/matplotlib/matplotlib/issues/4767 Both maybe addressed by https://github.com/matplotlib/matplotlib/pull/4878 or might be poor interaction with the auto-redraw in plain python repl + interactive mode Bugs (bugs that may have been there in 1.4) - python 3 related - https://github.com/matplotlib/matplotlib/issues/4908 - (PR for #4908) https://github.com/matplotlib/matplotlib/pull/4915 - https://github.com/matplotlib/matplotlib/pull/4910 (font config) - https://github.com/matplotlib/matplotlib/issues/4806 (formatting mouse over strings) - https://github.com/matplotlib/matplotlib/pull/4689 (font scoring) - plus the bugs in #4897 that I do not understand yet - https://github.com/matplotlib/matplotlib/pull/4912 (prefer qt5 to qt4 in a corner case) Critical bugs (regressions) - https://github.com/matplotlib/matplotlib/pull/4887 (mathtex accents, I put a major regression in, this fixes it and is ready to go) There are deeper issues related to the mathtext test suite (expansive, but too permissive), but punting on that for now. Unit related PRs - https://github.com/matplotlib/matplotlib/pull/4905 - https://github.com/matplotlib/matplotlib/pull/4904 Critical Documentation - https://github.com/matplotlib/matplotlib/pull/4779 This needs review and a bit more writing from me. One important thing to go in is that the per-artist stale state has a 2 year expiration if we do not find a use case for it. - https://github.com/matplotlib/matplotlib/issues/4783 (include the new color maps) - https://github.com/matplotlib/matplotlib/issues/4543 (house keeping on our docs) If anyone has bandwidth for review or to work on these things that would be great Tom

1 0

Status of MEP12
by Fabien Aug. 8, 2015

Aug. 8, 2015

Hi all, I've seen a lot of mep12 merges lately. Is it something that you guys could still need help with? I've seen a couple of examples where newcomers like me could provide easy fixes (for example: https://github.com/matplotlib/matplotlib/blob/master/examples/pylab_example… that should not be located in examples/pylab, or http://matplotlib.org/examples/api/colorbar_only.html that could be simplified). But since it seems to be quite an ongoing effort it might not be necessary to have too many people working on it. (as a side note, the MEP13 page has a wrong title: http://matplotlib.org/devdocs/devel/MEP/MEP13.html) cheers, Fabien

2 1