diff options
| author | Simon Tatham <anakin@pobox.com> | 2019-04-13 15:57:28 +0100 |
|---|---|---|
| committer | Simon Tatham <anakin@pobox.com> | 2019-04-13 15:57:28 +0100 |
| commit | 1ffc73713062736a1a5f255f5f8dec3de027269c (patch) | |
| tree | f3adc75213f1bd10b89c619929a5bf9788a33d23 /PuzzleApplet.java | |
| parent | 9f0dfba5fa9431469060ae89bef486267dbb23d4 (diff) | |
| download | puzzles-1ffc73713062736a1a5f255f5f8dec3de027269c.zip puzzles-1ffc73713062736a1a5f255f5f8dec3de027269c.tar.gz puzzles-1ffc73713062736a1a5f255f5f8dec3de027269c.tar.bz2 puzzles-1ffc73713062736a1a5f255f5f8dec3de027269c.tar.xz | |
Dominosa: move set analysis with doubles into Extreme.
This change doesn't alter the overall power of the Dominosa solver; it
just moves the boundary between Hard and Extreme so that fewer puzzles
count as Hard, and more as Extreme. Specifically, either of the two
cases of set analysis potentially involving a double domino with both
squares in the set is now classed as Extreme.
The effects on difficulty are that Hard is now easier, and Extreme is
at least easier _on average_. But the main purpose is the effect on
generation time: before this change, Dominosa Extreme was the slowest
puzzle present to generate in the whole collection, by a factor of
more than three. I think the forcing-chain deductions just didn't make
very many additional grids soluble, so that the generator had to try a
lot of candidates before finding one that could be solved using
forcing chains but not with all the other techniques put together.
Diffstat (limited to 'PuzzleApplet.java')
0 files changed, 0 insertions, 0 deletions