Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

5
  • \$\begingroup\$ Too bad you didn't win the bounty, I was really hoping an approach like this would take it - I've given you an "honourable mention" in the question. I'm looking forward to the explanation of how this was produced. \$\endgroup\$ Commented Feb 2, 2016 at 12:47
  • \$\begingroup\$ @Nathaniel I may have just missed the bounty by hours; my optimizer is still running, and I just reached 5000. \$\endgroup\$ Commented Feb 2, 2016 at 13:02
  • \$\begingroup\$ Well, you might be in luck - I already announced a second bounty if an optimisation based approach takes first place among the non-compression based answers. (See the updated question text.) \$\endgroup\$ Commented Feb 2, 2016 at 13:24
  • \$\begingroup\$ Heh, I was out to beat Sleafar (and he would have won anyway, since his score is lower than yours). Was quite surprised that the change I made (disabling dithering) made such a big impact. \$\endgroup\$ Commented Feb 2, 2016 at 16:16
  • \$\begingroup\$ +1 for Voronoi and for using a subplane of the RGB cube. Did you try using any of the answers from codegolf.stackexchange.com/q/50299/8478 to optimise the Voronoi diagram? (Of course, those were aiming at visual similarity, not minimising an objective error, so YMMV, but I think some of them might yield pretty good results.) Also, have you tried using just a line through the RGB cube so you can use twice as many Voronoi cells? \$\endgroup\$ Commented Feb 3, 2016 at 14:07