yzfwsf wrote:Now I can guarantee to generate puzzles of SE9.1 ~ 9.3 in 1 minute, generally no more than 30 seconds.
That's great !
yzfwsf wrote:Now I can guarantee to generate puzzles of SE9.1 ~ 9.3 in 1 minute, generally no more than 30 seconds.
denis_berthier wrote:If you have similar collections for skfr = 9.2 and skfr = 9.4, I'm curious to see how the proportion of puzzles in T&E(1) varies.
yzfwsf wrote:Please download 3 attachments, remove '. 7z' and unzip from '9+.7z.001'denis_berthier wrote:If you have similar collections for skfr = 9.2 and skfr = 9.4, I'm curious to see how the proportion of puzzles in T&E(1) varies.
champagne wrote:After the test run, skfr should very often rate in that area .1 or .2 below SE.
The reason is that SE fails very often in looking for the shortest path toward it's own rule.
I have however the following problem that could lead sometimes to a +0.1 in skfr rating.
In the dynamic process, you have many ways to establish a false for a candidate.
Depending on the order in which you develop the chains, it can be that the best possibility toward SE final count is not seen when I start the reverse search.
The test run in the "dynamic" area has moreover 4 goals:
a) check that the process works properly
b) check that the count is done strictly following SE rules
c) check that lower rating in skfr are justified
d) explain higher rating in skfr
I think a) is ok now up to level 2 and I start test for level 3.
All other items are still requiring comparative tests that need a lot of hand work.
At the end, d) should be the exception.
champagne
tarek wrote:I know this may open a can of worms but I thought that with the work on the Sukaku explainer (which doubles up as sudoku explainer as well), there could be a scope for SE ratings / Resolution rule order / Resolution rule addition/deletion.
The current rules & ratings (which occasionally) overlap are:
- Code: Select all
1.0: Last value in block, row or column
1.2: Hidden Single in block
1.5: Hidden Single in row or column
1.7: Direct Pointing
1.9: Direct Claiming
2.0: Direct Hidden Pair
2.3: Naked Single
2.5: Direct Hidden Triplet
2.6: Pointing
2.8: Claiming
3.0, 3.2, 3.4: Naked Pair, X-Wing, Hidden Pair
3.6, 3.8, 4.0: Naked Triplet, Swordfish, Hidden Triplet
4.2, 4.4: XY-Wing, XYZ-Wing
4.5 - 5.0: Unique rectangles and loops
5.0, 5.2, 5.4: Naked Quad, Jellyfish, Hidden Quad
5.6 - 6.0: Bivalue Universal Graves
6.2: Aligned Pair Exclusion
6.5 - 7.5: Bidirectioal X-Cycles and Y-Cycles
6.6 - 7.6: Forcing X-Chains
7.0 - 8.0: Forcing Chains, Bidirectional Cycles
7.5 - 8.5: Nishio
8.0 - 9.0: Cell/Region Forcing Chains
8.5 - 9.5: Dynamic Forcing Chains
9.0 - 10.0: Dynamic Forcing Chains (+)
> 9.5: Nested Forcing Chains
I'll start by 1st suggesting a change towards the lower end of the ratings as follows:
- Code: Select all
1.2: Hidden single (1.5 if not in block)
1.6: Naked single//2.3 ---> 1.6
1.7: Direct Pointing
1.9: Direct Claiming
2.0: Direct Hidden Pair
2.6: Pointing
2.8: Claiming
2.9: Hidden pair//3.4 ---> 2.9
3.0: Direct Hidden Triplet//2.5 ---> 3.0
3.1, 3.2: Naked pair, X-Wing//3.0 ---> 3.1
3.6, 3.8, 4.0: Naked triplet, Hidden triplet, Swordfish//3.8 ---> 4.0 4.0 ---> 3.8
4.2, 4.4: XY-Wing, XYZ-Wing
4.5 - 5.0: Unique Rectangles and Loops
5.0, 5.2, 5.4: Naked quad, Hidden quad, Jellyfish//5.2 ---> 5.4 5.4 ---> 5.2
5.6 - 6.0: Bivalue Universal Graves
6.2: Aligned Pair Exclusion
6.5 - 7.5: X-Cycles, Y-Cycles
6.6 - 7.6: Forcing X-Chains
7.0 - 8.0: Forcing Chains, XY-Cycles
7.5: Aligned Triplet Exclusion
7.5 - 8.5: Nishio
8.0 - 9.0: Multiple chains
8.5 - 9.5: Dynamic chains
9.0 - 10.0: Dynamic chains (+)
>9.5: Nested Forcing Chains
One thing I was considering is increasing the space between the current ratings through multiplying all the current ratings by 10 … But then: should we allow overlapping as it is happening now or not? The increase in space can allow adding more techniques in the future if needed …
tarek
yzfwsf wrote:I think ser9.1 ~ 9.3 fall into T & E (1), which should be a normal phenomenon, because as mentioned above,T & E (1) and T & E (2) overlap in 9.0 ~ 9.5 in SudokuExplainer
Out of curiosity, I generated random grids and then took out all clues not on mini-diagonals, thus:tarek wrote:denis_berthier wrote:AFAIK, there's been no study on any correlation between maximum number of clues per house and difficulty.
The 3 clue per house makes it more likely that boxes would display a "Diagonal pattern of clues": Which essentially can be mapped on an "X". Puzzles with boxes displaying these diagonal patterns are associated with higher SE difficulty rating.
7 . 3 2 . 8 4 . 1
. 2 . . 6 . . 3 .
4 . 1 7 . 3 2 . 8
2 . 6 5 . 7 1 . 9
. 7 . . 1 . . 2 .
8 . 4 9 . 2 6 . 5
3 . 2 1 . 4 9 . 6
. 9 . . 2 . . 4 .
6 . 5 3 . 9 7 . 2
. . 1 2 . 3 4 . 5
. . . . 1 . . 3 .
. . . 6 . . . . .
6 . 5 7 . . . . 8
. 1 . . 8 . . 2 .
. . 2 . . . 9 . .
. . . 3 . . . . .
. . . . . . . 9 .
3 . 7 . . 4 1 . 6 ED=9.0/2.3/2.3
. . 1 2 . 3 . . .
. 4 . . 5 . . 3 .
. . 6 . . 7 . . .
1 . . . . . 8 . .
. 8 . . 2 . . 4 .
. . 9 . . 8 3 . .
2 . . 6 . . 4 . 5
. . . . . . . 2 .
6 . 5 . . . . . 7 ED=9.1/1.2/1.2
1 . . . . 2 3 . .
. 4 . . 5 . . . .
. . 6 7 . 1 4 . .
3 . . . . 5 2 . .
. . . . 7 . . 3 .
7 . 8 2 . . . . 6
. . 2 . . 9 . . 8
. . . . 2 . . 9 .
. . 5 1 . . 6 . . ED=9.2/9.2/6.7
m_b_metcalf wrote:Out of curiosity, I generated random grids and then took out all clues not on mini-diagonals, thus:
- Code: Select all
7 . 3 2 . 8 4 . 1
. 2 . . 6 . . 3 .
4 . 1 7 . 3 2 . 8
2 . 6 5 . 7 1 . 9
. 7 . . 1 . . 2 .
8 . 4 9 . 2 6 . 5
3 . 2 1 . 4 9 . 6
. 9 . . 2 . . 4 .
6 . 5 3 . 9 7 . 2
yzfwsf wrote:m_b_metcalf wrote:Out of curiosity, I generated random grids and then took out all clues not on mini-diagonals, thus:
- Code: Select all
7 . 3 2 . 8 4 . 1
. 2 . . 6 . . 3 .
4 . 1 7 . 3 2 . 8
2 . 6 5 . 7 1 . 9
. 7 . . 1 . . 2 .
8 . 4 9 . 2 6 . 5
3 . 2 1 . 4 9 . 6
. 9 . . 2 . . 4 .
6 . 5 3 . 9 7 . 2
I'm curious how you got this non minimal puzzle and how much time it took?
denis_berthier wrote:yzfwsf wrote:m_b_metcalf wrote:Out of curiosity, I generated random grids and then took out all clues not on mini-diagonals, thus:
- Code: Select all
7 . 3 2 . 8 4 . 1
. 2 . . 6 . . 3 .
4 . 1 7 . 3 2 . 8
2 . 6 5 . 7 1 . 9
. 7 . . 1 . . 2 .
8 . 4 9 . 2 6 . 5
3 . 2 1 . 4 9 . 6
. 9 . . 2 . . 4 .
6 . 5 3 . 9 7 . 2
I'm curious how you got this non minimal puzzle and how much time it took?
When you take any complete grid and you randomly delete any set of 33 values as here, that leaves 48 givens. The probability that the resulting puzzle has more than one solution (Ie. any solution other than the initial complete grid) is so close to 0 that it's impossible to compute. As a result, the time it took is equal to the time for generating a full grid.
[Edit]: this is true only for random deletions. In the present case, the deleted clues are in fixed cells. I would bet the result is true in the present case, but there are probably counter-examples with other specific deletion templates (such as if you delete a full band).
7 6* 3 2 5* 8 4 9* 1
9 2 8 4 6 1 5 3 7
4 5* 1 7 9* 3 2 6* 8
2 3 6 5 4 7 1 8 9
5 7 9 8 1 6 3 2 4
8 1 4 9 3 2 6 7 5
3 8 2 1 7 4 9 5 6
1 9 7 6 2 5 8 4 3
6 4 5 3 8 9 7 1 2
m_b_metcalf wrote: But then I checked how many of the resulting puzzles have more than one solution and the answer was not, as Denis and I expected, close to 0, but 31%! I was very surprised. The reason is due to the regularity of the deletions.
Mauriès Robert wrote:denis_berthier wrote:I have a pure pattern-based resolution path. I will give it later, after more people give this puzzle a try. It is worth it.
I have already made a resolution by hand, I hope to give it soon.
Mauriès Robert wrote:I can send you these steps by private message if you want to see what I've done already.