Although I agree with Phillip that voting was not super-principled, I also
agree with you Tom that it's time to move on. All the above colormaps meet
stringent perceptibility criteria and so the vote comes down mostly to
aesthetics. As long as they are all named options, I for one will be happy.
T
As long as A and B are included as named options, I have no objections to D
as default. (From a branding perspective though, I preferred being closer
to GNUPlot than Matlab, but whatevs. Show MPL's roots I guess! =)
Juan.
On Wed, Jun 17, 2015 at 12:14 PM, Nathaniel Smith wrote:
> Greetings, mat
Fun activity: watch all 6 videos in a row then watch the text on this email
spin and spin. =P
Gorgeous! Thanks Nathan!
I hope this kills C dead. It clearly makes certain features of the
simulation harder to spot.
A great demo of the terribleness of jet, too: it looks like a huge mess.
On Thu, J
Andreas Hilboll wrote:
> On 03.06.2015 08:54, Juan Nunez-Iglesias wrote:
> > You can always use green for NaN with any of these maps...
>
> In grayscale that then wouldn't be distinguishable at all ...
>
> > On Wed, Jun 3, 2015 at 4:30 PM, Andreas Hilboll > &l
You can always use green for NaN with any of these maps...
—
Sent from Mailbox
On Wed, Jun 3, 2015 at 4:30 PM, Andreas Hilboll wrote:
>> I particularly like that A ends on the white end of the spectrum
> That's exactly why I don't like A that much.
> In many plots, I need a color for NaN result
It's astonishing how many different opinions we have!
Anyway, first of all, a big thank you to Nathaniel and Stéfan for some
kick-ass work. I'm amazed at the perceptual delta results for Parula... 8-O
Good to know that MPL will not make the same mistake.
Second, my preferences:
A > B > C.
I par
on.org/3.5/reference/expressions.html#calls for the
> official docs.
>
> I suspect the source of this bug is that the grammar is getting rearranged
> a bit to allow for things like d = {**other_dict, 'x':6} and b = (*a, *c)
> to work as expected and something di
Fascinating! Can you "unpack" (heh) that error for us mere mortals? In
particular:
- never seen that "or" syntax before... Is it coercing both expressions as
bool, or is it evaluating to left if bool(left) evaluates to True, else to
right?
- Why do you expect the second expression to work? Is ** s
<3 <3 <3 Love the prototype colormap!!!--
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 softwar
