Mauriès Robert wrote:I am surprised that you do not try to understand my definition of MSLS even when you ask me ( "May I ask what kind of notion of MSLS you do have then?" ), if only to tell me if it is good or bad.
I appreciate that you tried to answer that question, but I already told why it wasn't really helpful.
However, my explanations do not seem more theoretical than anything you have to say on this subject.
Oh please, give me a break. You gave a piece of theory written as a mathematical algorithm with meaningless variable names that weren't even defined anywhere. I wouldn't have accepted such lack of readability even from a computer program, much less from something meant for human consumption. Most importantly, there was not a single illustrating example with it, so there was a zero chance that I was going to waste my time even trying to decipher it. I already did with your TDP but won't do it again. (Btw, you demonstrated
here that you can in fact express TDP principles in simpler terms.)
On the other hand, I've provided several detailed
examples and explanations of everything I've presented, and they're all in standard sudoku languages. I even gave you a brief tutorial of the set logic notation and principles, even though it should be more or less standard knowledge in this context. However, it looks like I did all that for nothing, if you don't see the difference.
In fact, I manually digged up and presented as many related Rank 0 patterns for the same puzzle state as I could, which is something no one has published before, as far as I know. It's something you can't get out of Phil's (public) solver, for example, because it only shows you the first one of any pattern type it finds -- leaving the impression that nothing else is available. It's enough for getting a working result, but not enough to gain a complete understanding.
But anyway, here's an example to better explain my definition, with this puzzle from Phil's website.
Like I've said, concrete examples are the
bare minimum you need to provide if you publish your theories and expect me to read them. So thanks for that, finally. However, I'm still not going to study your mathematical expressions filled with single-letter indexed variables, simply because I don't like to read them. That's why examples are crucial, because they're probably the only things I even look at. From those I can usually see the intended logic without reading the boring theory (and if not, then I might get more interested in the latter).
I do sudoku for entertainment purposes, so in this context I simply refuse to do anything I don't enjoy unless it seems to have an extremely high payoff probability. I'm sorry to say but I don't enjoy reading your mathematical explanations so they're lost on me, just like some of David's were for slightly different reasons. Quite clearly you like to think and express your ideas in those terms, and that's your choice, but I'm just telling that it's also my choice to skip them in that case. I said the same about TDP so it shouldn't come as a surprise for you. (Btw, several people have complained about my style too, so it's not like I'm claiming to be any better. Just different.)
Anyway, about your example, here's the two complementary MSNSs I could easily find manually. The first one is the same as what Phil's solver presents and what your diagram depicts:
- Code: Select all
\457 \37 \346 \45 \36
.--------------------------.---------------------------.--------------------------.
| 1 *24579 *2379 | *246 *245 4567-2 | 3467 8 *369 | \29
| 3457-8 *4578 *378 | *1468 *1458 9 | 2 3467 *136 | \18
| 4789 289-47 6 | 128-4 3 1247 | 147 479 5 |
:--------------------------+---------------------------+--------------------------:
| 2 *1479 *1379 | *13469 *149 8 | 3567-1 3567-9 *1369 | \19
| 3489 189-4 5 | 129-346 7 12346 | 1368 2369 1289-36 |
| 3789 6 189-37 | 5 129 123 | 1378 2379 4 |
:--------------------------+---------------------------+--------------------------:
| 5689 1289-5 4 | 7 1289-5 1235 | 3568 2356 28-36 |
| 567-8 *2578 *278 | *2348 *2458 345-2 | 9 1 *2368 | \28
| 589 3 1289 | 1289 6 125 | 458 245 7 |
'--------------------------'---------------------------'--------------------------'
4x5 MSNS: (1289)r1248 x (34567)c23459
20\20 (Rank 0): {1248N23459 \ 29r1 18r2 19r4 28r8 457c2 37c3 346c4 45c5 36c9} => 21 elims
If you look at the row and column markings (similar to David's), they're the same pairs as what you have within the cells in your diagram. So, just based on that observation, your algorithm is probably equivalent (though I haven't read it, for reasons explained above). It just seems more tedious to use if it requires drawing a separate grid.
This took me a few minutes, including spotting the MSLS, confirming Rank 0 status, finding the eliminations, and writing it with unambiguous set logic notation. Marking the grid for presentation took longer.
Here's the complementary MSNS that Phil's solver doesn't show:
- Code: Select all
\89 \12 \18 \29
.-------------------------.--------------------------.---------------------------.
| 1 24579 2379 | 246 245 4567-2 | 3467 8 369 |
| 3457-8 4578 378 | 1468 1458 9 | 2 3467 136 |
| *4789 289-47 6 | 128-4 3 *1247 | *147 *479 5 | \47
:-------------------------+--------------------------+---------------------------:
| 2 1479 1379 | 13469 149 8 | 3567-1 3567-9 1369 |
| *3489 189-4 5 | 129-346 7 *12346 | *1368 *2369 1289-36 | \346
| *3789 6 189-37 | 5 129 *123 | *1378 *2379 4 | \37
:-------------------------+--------------------------+---------------------------:
| *5689 1289-5 4 | 7 1289-5 *1235 | *3568 *2356 28-36 | \356
| 567-8 2578 278 | 2348 2458 345-2 | 9 1 2368 |
| *589 3 1289 | 1289 6 *125 | *458 *245 7 | \45
'-------------------------'--------------------------'---------------------------'
5x4 MSNS: (34567)r35679 x (1289)c1678
20\20 (Rank 0): {35679N1678 \ 47r3 346r5 37r6 356r7 45r9 89c1 12c6 18c7 29c8} => 21 elims
The same digit sets can also produce multi-fishes, but I don't bother with them now.