Re: [matplotlib-devel] Alternative way of specifying plot layout

[Nicolas P. Rougier]

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  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  
> 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  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 
>>  wrote:
>> 
>> I think you could specify colorbars using: ["AB"]
>> (B is a vertical colorbar, 1/10 of total width)
>> 
>> Nicolas
>> 
>> 
>> 
>> > On 18 Mar 2015, at 18:52, Eric Firing  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@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/
>> ___
>> Ma

Re: [matplotlib-devel] backporting the boxplot fix

[Mike Kaufman]

So it seems I was using the old branch (now deleted?) v1.4.x rather than 
v1.4.3-doc, which does have the commit for the fix in question. I was 
naively assuming that v1.4.x was always the latest release in the v1.4 
series.

False alarm. Sorry.

M

On 4/25/15 4:26 PM, Thomas Caswell wrote:
> The commit that fixes that
> https://github.com/matplotlib/matplotlib/commit/40720ef9fb5de75d908d0ce433d5c3bb8902884f
> should be in 1.4.1 an onward.  Exactly which version are you using?
>
> There will be no 1.4.4.
>
> On Tue, Apr 21, 2015 at 11:00 AM Michael Kaufman  > wrote:
>
> Is there any possibility of back-porting the fix to the boxplot
> positions to v1.4.x? This would be ticket #3563. I had thought that this
> was fixed in 1.4, but it seems to be there again. v1.5-devel (where the
> boxplot works fine) is not-very-usable for me due to the GTK idle bug.
>
> Thanks,
>
> M
>
> 
> --
> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> Develop your own process in accordance with the BPMN 2 standard
> Learn Process modeling best practices with Bonita BPM through live
> exercises
> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual-
> event?utm_
> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
> ___
> Matplotlib-devel mailing list
> Matplotlib-devel@lists.sourceforge.net
> 
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
>
>
> --
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
>
>
>
> ___
> Matplotlib-devel mailing list
> Matplotlib-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>


--
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel

Re: [matplotlib-devel] Alternative way of specifying plot layout

[Thomas Caswell]

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 
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  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.roug...@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  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.roug...@inria.fr> wrote:
> >>
> >> I think you could specify colorbars using: ["AB"]
> >> (B is a vertical colorbar, 1/10 of total width)
> >>
> >> Nicolas
> >>
> >>
> >>
> >> > On 18 Mar 2015, at 18:52, Eric Firing  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@lists.sourceforge.net
> >> > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
> >>
> >>
> >>
> --
> >> Dive into the World of Parallel Programming The Go

Re: [matplotlib-devel] backporting the boxplot fix

[Thomas Caswell]

The branch 1.4.x was the branch for bug fixes that would eventually turn
into the _next_ 1.4 series release.  We do not plan on doing a 1.4.4 so the
1.4.x branch no longer is needed.  The commit used for the releases are
tagged (ex v1.4.3).  The v1.4.3-doc branch is so that we can correct any
documentation issues and re-build the website if needed.

Tom

On Sun, Apr 26, 2015 at 9:12 AM Mike Kaufman  wrote:

> So it seems I was using the old branch (now deleted?) v1.4.x rather than
> v1.4.3-doc, which does have the commit for the fix in question. I was
> naively assuming that v1.4.x was always the latest release in the v1.4
> series.
>
> False alarm. Sorry.
>
> M
>
> On 4/25/15 4:26 PM, Thomas Caswell wrote:
> > The commit that fixes that
> >
> https://github.com/matplotlib/matplotlib/commit/40720ef9fb5de75d908d0ce433d5c3bb8902884f
> > should be in 1.4.1 an onward.  Exactly which version are you using?
> >
> > There will be no 1.4.4.
> >
> > On Tue, Apr 21, 2015 at 11:00 AM Michael Kaufman  > > wrote:
> >
> > Is there any possibility of back-porting the fix to the boxplot
> > positions to v1.4.x? This would be ticket #3563. I had thought that
> this
> > was fixed in 1.4, but it seems to be there again. v1.5-devel (where
> the
> > boxplot works fine) is not-very-usable for me due to the GTK idle
> bug.
> >
> > Thanks,
> >
> > M
> >
> >
>  
> --
> > BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> > Develop your own process in accordance with the BPMN 2 standard
> > Learn Process modeling best practices with Bonita BPM through live
> > exercises
> > http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual-
> > event?utm_
> >
>  source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
> > ___
> > Matplotlib-devel mailing list
> > Matplotlib-devel@lists.sourceforge.net
> > 
> > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
> >
> >
> >
> >
> --
> > One dashboard for servers and applications across Physical-Virtual-Cloud
> > Widest out-of-the-box monitoring support with 50+ applications
> > Performance metrics, stats and reports that give you Actionable Insights
> > Deep dive visibility with transaction tracing using APM Insight.
> > http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> >
> >
> >
> > ___
> > Matplotlib-devel mailing list
> > Matplotlib-devel@lists.sourceforge.net
> > https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
> >
>
>
>
> --
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
> ___
> Matplotlib-devel mailing list
> Matplotlib-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>
--
One dashboard for servers and applications across Physical-Virtual-Cloud 
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
http://ad.doubleclick.net/ddm/clk/290420510;117567292;y___
Matplotlib-devel mailing list
Matplotlib-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel