matplotlib-devel Mailing List for matplotlib

We would like to tag 1.5 around scipy and it would be nice to get the new
color maps out, even if they are not yet the default.
On Wed, Jul 1, 2015, 11:13 PM Nathaniel Smith <nj...@po...> wrote:
> On Jul 1, 2015 6:31 PM, "Eric Firing" <ef...@ha...> wrote:
> >
> > On 2015年07月01日 1:56 PM, Nathaniel Smith wrote:
> > > On Tue, Jun 16, 2015 at 7:14 PM, Nathaniel Smith <nj...@po...>
> wrote:
> > >
> > > [...snip discussion of how option D was the favorite of 80% of people
> > > in the survey...]
> > >
> > >> So the next question is where we go from here.
> >
> > One thing we need to do is get some of these maps into _cm.py via PR.
>
> We've been a bit distracted getting the software and talk together ahead
> of scipy, but PR (with names) will follow within the next week or so. The
> decision part is pretty orthogonal though I think? It's not like matplotlib
> 2.0 is going to branch between now and scipy :-).
>
> > I would prefer not to have them go in as huge tables if they can be made
> > more compact, either by being function-generated or by using the
> > LinearSegmentedColormap mechanism with a moderate number of breakpoints.
> >
> > Suggestions?
>
> Depends on how you define "moderate", but my guess is that linear
> segmented is the best approach -- the exact colormaps have a pretty terse
> representation as bezier control points, but using this at runtime would
> require pulling in the full colorspace apparatus as a dependency. Which I
> guess has points in its favor for other reasons, but nonetheless.
>
> These kinds of details can be worked out in the PR review process, though.
> The blocking issue is that we need a decision :-).
>
> -n
>
> ------------------------------------------------------------------------------
> 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
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

On Jul 1, 2015 6:31 PM, "Eric Firing" <ef...@ha...> wrote:
>
> On 2015年07月01日 1:56 PM, Nathaniel Smith wrote:
> > On Tue, Jun 16, 2015 at 7:14 PM, Nathaniel Smith <nj...@po...> wrote:
> >
> > [...snip discussion of how option D was the favorite of 80% of people
> > in the survey...]
> >
> >> So the next question is where we go from here.
>
> One thing we need to do is get some of these maps into _cm.py via PR.
We've been a bit distracted getting the software and talk together ahead of
scipy, but PR (with names) will follow within the next week or so. The
decision part is pretty orthogonal though I think? It's not like matplotlib
2.0 is going to branch between now and scipy :-).
> I would prefer not to have them go in as huge tables if they can be made
> more compact, either by being function-generated or by using the
> LinearSegmentedColormap mechanism with a moderate number of breakpoints.
>
> Suggestions?
Depends on how you define "moderate", but my guess is that linear segmented
is the best approach -- the exact colormaps have a pretty terse
representation as bezier control points, but using this at runtime would
require pulling in the full colorspace apparatus as a dependency. Which I
guess has points in its favor for other reasons, but nonetheless.
These kinds of details can be worked out in the PR review process, though.
The blocking issue is that we need a decision :-).
-n

Not my cup of tea, but to get the ball rolling, how about "Truncated Rainbow"? [Red, Orange, Yellow, Green, Blue, Indigo, Violet][2:]
 From: Benjamin Root <ben...@ou...>
 To: Eric Firing <ef...@ha...> 
Cc: matplotlib development list <mat...@li...> 
 Sent: Thursday, 2 July 2015, 4:19
 Subject: Re: [matplotlib-devel] Colormap survey results
 
I have been thinking a bit about naming. We could always go the route of "Heinz 57", "Chanel No. 5", or "Preparation H". Not saying that "MPL-d" is a catchy name or not, but.. :-P
Ben Root
On Wed, Jul 1, 2015 at 9:31 PM, Eric Firing <ef...@ha...> wrote:
On 2015年07月01日 1:56 PM, Nathaniel Smith wrote:
> On Tue, Jun 16, 2015 at 7:14 PM, Nathaniel Smith <nj...@po...> wrote:
>
> [...snip discussion of how option D was the favorite of 80% of people
> in the survey...]
>
>> So the next question is where we go from here.
One thing we need to do is get some of these maps into _cm.py via PR.
I would prefer not to have them go in as huge tables if they can be made
more compact, either by being function-generated or by using the
LinearSegmentedColormap mechanism with a moderate number of breakpoints.
Suggestions?
(We will also need a naming scheme.)
Eric
------------------------------------------------------------------------------
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
Mat...@li...
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
------------------------------------------------------------------------------
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
Mat...@li...
https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
 

I have been thinking a bit about naming. We could always go the route of
"Heinz 57", "Chanel No. 5", or "Preparation H". Not saying that "MPL-d" is
a catchy name or not, but.. :-P
Ben Root
On Wed, Jul 1, 2015 at 9:31 PM, Eric Firing <ef...@ha...> wrote:
> On 2015年07月01日 1:56 PM, Nathaniel Smith wrote:
> > On Tue, Jun 16, 2015 at 7:14 PM, Nathaniel Smith <nj...@po...> wrote:
> >
> > [...snip discussion of how option D was the favorite of 80% of people
> > in the survey...]
> >
> >> So the next question is where we go from here.
>
> One thing we need to do is get some of these maps into _cm.py via PR.
> I would prefer not to have them go in as huge tables if they can be made
> more compact, either by being function-generated or by using the
> LinearSegmentedColormap mechanism with a moderate number of breakpoints.
>
> Suggestions?
>
> (We will also need a naming scheme.)
>
> Eric
>
>
>
> ------------------------------------------------------------------------------
> 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
> Mat...@li...
> https://lists.sourceforge.net/lists/listinfo/matplotlib-devel
>

On 2015年07月01日 1:56 PM, Nathaniel Smith wrote:
> On Tue, Jun 16, 2015 at 7:14 PM, Nathaniel Smith <nj...@po...> wrote:
>
> [...snip discussion of how option D was the favorite of 80% of people
> in the survey...]
>
>> So the next question is where we go from here.
One thing we need to do is get some of these maps into _cm.py via PR. 
I would prefer not to have them go in as huge tables if they can be made 
more compact, either by being function-generated or by using the 
LinearSegmentedColormap mechanism with a moderate number of breakpoints.
Suggestions?
(We will also need a naming scheme.)
Eric