Mike Bostock

```js const i1 = d3.interpolateLab(color1, color2); const i2 = d3.interpolateLab(color3, color4); const i3 = d3.interpolateLab(i1(t1), i2(t1)); return i3(t2); ```

You’re describing a multivariate color scheme, not a bivariate one.

@mjmdavis Keys are required to be strings. https://github.com/d3/d3-selection#selection_data > A key function may be specified to control which datum is assigned to which element, replacing the default join-by-index, by computing...

Yes, that’s historically why D3 hasn’t included a special API for this case and encourages you to use *selection*.join instead. But I think it’s totally reasonable to special-case the enter...

In general, no. We’d need a `d3.bigsum` if we wanted to be accurate with respective to BigInt. You can coerce to Number as @Fil suggested if you don’t actually need...

I see value in doing this on the Cubism side, although it might also be nice to have Graphite do it; smoothing is a pretty useful feature to mitigate noise...

The metric operators derive a new metric, which in this case would compose the original metric with a smoothing function. So _metric.subtract(50)_ doesn’t modify the _metric_, it returns a new...

The context listens for arrow key events to control the focused time. See [context.js](https://github.com/square/cubism/blob/master/src/context.js#L114-127). I think if you want to fix this, you'll either need a way to disable keyboard...

You might be able to summarize(metric, "10s").

I’m not sure it’s sufficiently useful (meaning: essential) to add to the API. If it’s your code that’s calling context.start and context.stop, you can coordinate that method call with other...