From: Nathaniel S. <nj...@po...> - 2015-07-02 03:13:19
|
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 |