You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Adding names to the color in the new (Vega) default color cycle #7248
(using green for positive values and red for negative values is a not so rare convention).
(Of course, just using "g" and "r" or whatever CSS/XKCD color names doesn't really work either if you want to blend well with other figure elements that use the Vega10 palette.)
Thus, I'd suggest adding names to the colors of the Vega10/Vega20 palette, e.g. using the "vega:" prefix. Something like "blue", "orange", "green", "red", "purple", "brown", "pink", "gray", "yellow", "cyan" (all prefixed by "vega:" -- I don't think we can use "v:" due to the possible confusion with the triangle_down marker -- depends on the exact way the parser works...) looks close to what the colors are. The Vega20 palette (which adds lighter versions of all colors) can be supported as "vega:lightblue", etc. See https://github.com/vega/vega/wiki/Scales#scale-range-literals for the full palette.
Thoughts? The implementation itself is easy of course (just add the names to the named colors dict).
I think this should be milestoned to 2.0 or 2.0.1.
Reacted by Adrien F. Vincent, Vital Fernández and endolith
Not sure if I can use names from these references and try to match the color in vega cycle with those name using my naked eyes. Or any better way to do that?
It'd be easier to find names if we had a way to see all colors that need to be named.
I do think that steelblue and saddlebrown are sligthtly loo long and too hard to remember, so if we can avoid those and stick to easy ones (vega:oranage, vega:blue), that be nicer.
Updated OP with link to the Vega palettes. I think that because these will be the default colors, we should stick to relatively short names.
As a side note, http://matplotlib.org/devdocs/examples/color/named_colors.html should be updated (I guess we'll have a new VEGA_COLORS dict). It may also make sense to sort the colors first by "category" in that plot (1. one-letter, 2. Vega, 3. CSS).
Looking at the colour code _color_data.py I see we already have the xkcd names in there so that eradicates the need for separate fancy colour names as I see it.
With the namespace, I suggest we put in the list of 20 colours as blue, lightblue, orange, lightorange, etctera, perhaps with a space or underscore, and then simply skip the light colours for assigning to the default prop_cycle, with d3 [::2].
We brainstormed today to find the color names of all possible colors in the vega cycles. We aimed at having only one namespace, and here is what we came up with.
I think we've nailed it down for category 10 and 20
@tacaswell Any word back from Tableau? Did you just try their main contact, or did you also try some of the specific people in the company, like the person who wrote the blog post cited above for how they devised their new colour scheme.
I am talking to specific people, I'll update as soon as I know anything new. I am being a bit circumspect as I do not know if everyone on those email threads is ok with them being public.
Please do not start a second strand of inquiry with them.
Of course not, I wouldn't dream of imposing myself like that.
It has been two weeks though so I wondered if anything had come of it. I really love the colour scheme, especially for matplotlib and to come clean I have some public projects which I want to use it on ASAP, so I would like the all clear.
P.S. I should really try and come onto the Skype meetings. I shall try and free myself up to do so.
I like most of those colour names and agree with most of them. Category 10 and 20 look good, as does 20c, generally.
For 20b, it would be nice if all the colours did not correspond with the main 10 colours. That would emphasize that they are in a different set without having to modify the prefix explicitly. The red and pink in 20b don't really match with 10's red and pink, so I think that's also a good reason not to call them that as well. Using magenta for 20b's pink seems reasonable, and for 20b's red, maybe coral or salmon (but definitely not pink).
Also, there should probably be a grey alias for the gray.
referred to the new MPL 2.0 default green and red, so we could access them as easily as we could before, instead of using meaningless names like "C0" and "C1".
Activity
tacaswell commentedon Oct 11, 2016
Can not hurt, but we should make sure there is not an existing set of names for them.
I am pretty 😐 on this.
NelleV commentedon Oct 11, 2016
I think that's a good idea
anntzer commentedon Oct 11, 2016
@NelleV Can the machine shop do this? :)
NelleV commentedon Oct 11, 2016
The machine shop sure can!
anntzer commentedon Oct 11, 2016
Doing the literature search suggested by @tacaswell (check whether they already have standard names) is also part of the assignment, hehe...
trpham commentedon Oct 17, 2016
Not sure if I can use names from these references and try to match the color in vega cycle with those name using my naked eyes. Or any better way to do that?
https://xkcd.com/color/rgb/
https://en.wikipedia.org/wiki/X11_color_names
https://en.wikipedia.org/wiki/Web_colors
http://ingridsundberg.com/2014/02/04/the-color-thesaurus/
http://chir.ag/projects/name-that-color/#D62728
Also, something like: 'vega:steelblue' (for #1f77b4 ), 'vega:sienna' or 'vega:saddlebrown'( for #8c564b ) is hard to remember and long?
NelleV commentedon Oct 17, 2016
It'd be easier to find names if we had a way to see all colors that need to be named.
I do think that steelblue and saddlebrown are sligthtly loo long and too hard to remember, so if we can avoid those and stick to easy ones (vega:oranage, vega:blue), that be nicer.
anntzer commentedon Oct 17, 2016
Updated OP with link to the Vega palettes. I think that because these will be the default colors, we should stick to relatively short names.
As a side note, http://matplotlib.org/devdocs/examples/color/named_colors.html should be updated (I guess we'll have a new VEGA_COLORS dict). It may also make sense to sort the colors first by "category" in that plot (1. one-letter, 2. Vega, 3. CSS).
NelleV commentedon Oct 18, 2016
If I am not mistaken, it is only the first ten. There are only two redundant color (blue and green) so it should be quite straightforward
tacaswell commentedon Oct 18, 2016
We should probably consult @jheer on these names (I have also sent him a private email, but he is out on paternity leave this semester).
It is probably worth tracking down one of his students?
tacaswell commentedon Oct 18, 2016
Also, this is tagged 'Easy', but naming thing is one of the two hard problems in CS:
17 remaining items
OceanWolf commentedon Oct 19, 2016
Looking at the colour code
_color_data.pyI see we already have the xkcd names in there so that eradicates the need for separate fancy colour names as I see it.With the namespace, I suggest we put in the list of 20 colours as blue, lightblue, orange, lightorange, etctera, perhaps with a space or underscore, and then simply skip the light colours for assigning to the default prop_cycle, with
d3 [::2].trpham commentedon Nov 1, 2016
The proposed naming convention that we are coming up with.

NelleV commentedon Nov 1, 2016
We brainstormed today to find the color names of all possible colors in the vega cycles. We aimed at having only one namespace, and here is what we came up with.
I think we've nailed it down for category 10 and 20
OceanWolf commentedon Nov 2, 2016
@tacaswell Any word back from Tableau? Did you just try their main contact, or did you also try some of the specific people in the company, like the person who wrote the blog post cited above for how they devised their new colour scheme.
tacaswell commentedon Nov 2, 2016
I am talking to specific people, I'll update as soon as I know anything new. I am being a bit circumspect as I do not know if everyone on those email threads is ok with them being public.
Please do not start a second strand of inquiry with them.
OceanWolf commentedon Nov 2, 2016
Of course not, I wouldn't dream of imposing myself like that.
It has been two weeks though so I wondered if anything had come of it. I really love the colour scheme, especially for matplotlib and to come clean I have some public projects which I want to use it on ASAP, so I would like the all clear.
P.S. I should really try and come onto the Skype meetings. I shall try and free myself up to do so.
QuLogic commentedon Nov 10, 2016
I like most of those colour names and agree with most of them. Category 10 and 20 look good, as does 20c, generally.
For 20b, it would be nice if all the colours did not correspond with the main 10 colours. That would emphasize that they are in a different set without having to modify the prefix explicitly. The red and pink in 20b don't really match with 10's red and pink, so I think that's also a good reason not to call them that as well. Using magenta for 20b's pink seems reasonable, and for 20b's red, maybe coral or salmon (but definitely not pink).
Also, there should probably be a grey alias for the gray.
endolith commentedon Jan 18, 2017
It would be nice if
referred to the new MPL 2.0 default green and red, so we could access them as easily as we could before, instead of using meaningless names like "C0" and "C1".
NelleV commentedon Jan 18, 2017
Hi @endolith
You can now refer to the colors as
tab:blue,tab:orangeetc.NelleV commentedon Jan 18, 2017
I'm closing this issue, but we should probably document the color naming better.
tacaswell commentedon Jan 18, 2017
The nice thing about the 'CN' names is that they will always track your current color cycle.