Andrew Cooke | Contents | Latest | RSS | Previous | Next


Welcome to my blog, which was once a mailing list of the same name and is still generated by mail. Please reply via the "comment" links.

Always interested in offers/projects/new ideas. Eclectic experience in fields like: numerical computing; Python web; Java enterprise; functional languages; GPGPU; SQL databases; etc. Based in Santiago, Chile; telecommute worldwide. CV; email.

Personal Projects

Choochoo Training Diary

Last 100 entries

Surprise Paradox; [Books] Good Author List; [Computing] Efficient queries with grouping in Postgres; [Computing] Automatic Wake (Linux); [Computing] AWS CDK Aspects in Go; [Bike] Adidas Gravel Shoes; [Computing, Horror] Biological Chips; [Books] Weird Lit Recs; [Covid] Extended SIR Models; [Art] York-based Printmaker; [Physics] Quantum Transitions are not Instantaneous; [Computing] AI and Drum Machines; [Computing] Probabilities, Stopping Times, Martingales; bpftrace Intro Article; [Computing] Starlab Systems - Linux Laptops; [Computing] Extended Berkeley Packet Filter; [Green] Mainspring Linear Generator; Better Approach; Rummikub Solver; Chilean Poetry; Felicitations - Empowerment Grant; [Bike] Fixing Spyre Brakes (That Need Constant Adjustment); [Computing, Music] Raspberry Pi Media (Audio) Streamer; [Computing] Amazing Hack To Embed DSL In Python; [Bike] Ruta Del Condor (El Alfalfal); [Bike] Estimating Power On Climbs; [Computing] Applying Azure B2C Authentication To Function Apps; [Bike] Gearing On The Back Of An Envelope; [Computing] Okular and Postscript in OpenSuse; There's a fix!; [Computing] Fail2Ban on OpenSuse Leap 15.3 (NFTables); [Cycling, Computing] Power Calculation and Brakes; [Hardware, Computing] Amazing Pockit Computer; Bullying; How I Am - 3 Years Post Accident, 8+ Years With MS; [USA Politics] In America's Uncivil War Republicans Are The Aggressors; [Programming] Selenium and Python; Better Walking Data; [Bike] How Fast Before Walking More Efficient Than Cycling?; [COVID] Coronavirus And Cycling; [Programming] Docker on OpenSuse; Cadence v Speed; [Bike] Gearing For Real Cyclists; [Programming] React plotting - visx; [Programming] React Leaflet; AliExpress Independent Sellers; Applebaum - Twilight of Democracy; [Politics] Back + US Elections; [Programming,Exercise] Simple Timer Script; [News] 2019: The year revolt went global; [Politics] The world's most-surveilled cities; [Bike] Hope Freehub; [Restaurant] Mama Chau's (Chinese, Providencia); [Politics] Brexit Podcast; [Diary] Pneumonia; [Politics] Britain's Reichstag Fire moment; install cairo; [Programming] GCC Sanitizer Flags; [GPU, Programming] Per-Thread Program Counters; My Bike Accident - Looking Back One Year; [Python] Geographic heights are incredibly easy!; [Cooking] Cookie Recipe; Efficient, Simple, Directed Maximisation of Noisy Function; And for argparse; Bash Completion in Python; [Computing] Configuring Github Jekyll Locally; [Maths, Link] The Napkin Project; You can Masquerade in Firewalld; [Bike] Servicing Budget (Spring) Forks; [Crypto] CIA Internet Comms Failure; [Python] Cute Rate Limiting API; [Causality] Judea Pearl Lecture; [Security, Computing] Chinese Hardware Hack Of Supermicro Boards; SQLAlchemy Joined Table Inheritance and Delete Cascade; [Translation] The Club; [Computing] Super Potato Bruh; [Computing] Extending Jupyter; Further HRM Details; [Computing, Bike] Activities in ch2; [Books, Link] Modern Japanese Lit; What ended up there; [Link, Book] Logic Book; Update - Garmin Express / Connect; Garmin Forerunner 35 v 230; [Link, Politics, Internet] Government Trolls; [Link, Politics] Why identity politics benefits the right more than the left; SSH Forwarding; A Specification For Repeating Events; A Fight for the Soul of Science; [Science, Book, Link] Lost In Math; OpenSuse Leap 15 Network Fixes; Update; [Book] Galileo's Middle Finger; [Bike] Chinese Carbon Rims; [Bike] Servicing Shimano XT Front Hub HB-M8010; [Bike] Aliexpress Cycling Tops; [Computing] Change to ssh handling of multiple identities?; [Bike] Endura Hummvee Lite II; [Computing] Marble Based Logic; [Link, Politics] Sanity Check For Nuclear Launch; [Link, Science] Entropy and Life

© 2006-2017 Andrew Cooke (site) / post authors (content).

Rummikub Solver

From: andrew cooke <andrew@...>

Date: Thu, 12 Jan 2023 16:48:36 -0300

I have been working on a solver for Rummikub, but I haven't actually
made much progress.  This email is to note down some of my ideas and
related issues.

The underlying insight is that this is a graph colouring problem.  The
nodes of the graph are the known tiles.  Edges connect any two tiles
that can appear "next to each other" in a group.  The colouring
identifies each group (a successful colouring meets the appropriate

There may be an efficiency gain in using the previous colouring as a
starting point when searching for a new one.

This is fine as far as it goes.  It becomes more problematic when you
include jokers.

A naive first approach is to include the jokers as additional nodes.
The problem is that these are connected to *every* other node.  This
complicates hugely the search process when trying t find a colouring.

In practice, when you play, you tend to separate things into two
stages: first, liberating a joker and second, using that joker.

Using this approach the joker tiles become "normal" tiles in the graph
(ie take their assumed values) when searching for liberation.  Then,
in the next step, thereare many possible graphs (one for each possible
value of the joker).

I currently don't see how to handle this explosion in the number of

So I'm stuck. It seems like the colouring view doesn't reduce the
combinatorial complexity sufficiently.  Or doesn't allow for the
complexity to be reduced using a "natural" compromise.


Better Approach

From: andrew cooke <andrew@...>

Date: Sat, 21 Jan 2023 19:56:42 -0300

In the note above I modeled the game as a graph with colourings.  But
things kinda fell apart because I needed multiple graphs.

After thinking some more, it may be better to ditch colourings
altogether and simply search for graphs.  These graphs have
connections only where there are "played" relationships between the

Now, the problem with this is that there are an awful lot of possible
graphs.  How do you generate them efficiently (where efficiency
includes memory, speed, and accuracy (generating no or few
"impossible" graphs))?

It seems like there may be a sweet-spot implementation that uses
association tables where each row is in fact a list.  Each entry in
the list describes a locally-consistent set of neigbours (so, for
example, a neigbour that belongs to a run and another that belongs to
a group would not appear in the list together).

To first aproximation the graphs we want to generate are then all the
different combinations possible by selecting one list entry from each

But that ignores remote (contrast w local) consistency - if a node A
has selected node B as part of a run then node B must select A as part
of a run too (for example).

So one can imagine a search process in which selecting a list entry
for one node constraints the available list entries in neghbouring
nodes (in fact, constraints can cascade across multiple connections,
which complicaes things somewhat).  I think this would be most
efficient as a "push" - then the entry is selected all neighbours are
corrected immediately.

Thinking in more detail about the implementation, each list entry
might have a tag that indicates whether it is a run or group locally.
That tag could then have a third value - unused - when filtered by
remote constraints (and maybe a fourth indicating that the tile is

A further advantage of this approach is that jokers are more naturally
handled (their "assumed value" can be stored in the list entry?).


Comment on this post