ghfick wrote:Of course both steps are valid. I was attempting to address the namings.
Which is fine, but you got it wrong.
YZF_Sudoku calls the one with the box 1 connection a 'Grouped Almost Locked Set W-Wing' and it calls the one with the column 2 connection a 'Death Blossom'.
I don't have YZF_Sudoku so I can't know what it uses, but I seriously doubt that
yzfwsf would make elementary mistakes like that. I haven't seen him make mistakes at all. Most likely you're looking at totally different moves using different candidates and logic, even if they're using the same
cells. (That said, I don't see any Grouped ALS W-Wing in those cells.)
Isn't the image you posted taken from YZF_Sudoku? Did it not call it Grouped W-Wing? I assume it did because you presented it as such. If it did, then it got it right, as I would expect. Are you claiming that it calls the exact same pattern "Grouped ALS W-Wing" too? I seriously doubt it, because it's not. If you disagree, please post the image of YZF's move.
[Added. That's no longer necessary. It appears that my assumption was wrong, and YZF did in fact use a wrong name.]As for the column 2 variant, look at
Cenoman's solution above. That is indeed a Death Blossom (as it was correctly called) which uses the same cells as my Grouped W-Wing. The difference is that it uses the candidates 6r67c2 which are not part of the W-Wing logic at all. It could also be expressed as an ALS-XZ: (481=6)b4p328 - (6=784)b7p281 => -4 r5c1,r7c3. The W-Wing can't be.
HoDoKu calls it the one with the column 2 connection an 'Almost Locked Set Chain'.
Hodoku doesn't even have a concept of Grouped W-Wing, so of course you can't find that move there with that name. You most certainly can't find it as an "ALS Chain" because it's not. Again you're looking at a totally different move without realizing it. What you should find instead is this:
Hodoku wrote:- Code: Select all
.---------------------.----------------.------------------.
| 589 2 578 | 3 6 4789 | 1 4578 458 |
| 689 4 678 | 79 1 5 | 2 3 68 |
| 1568 3 15678 | 47 2 478 | 4678 4578 9 |
:---------------------+----------------+------------------:
| 2 *18 *48 | 6 79 1479 | 5 1478 3 |
| -46 5 3 | 2 8 147 | 467 9 146 |
| 7 *168 9 | 14 5 3 | 468 148 2 |
:---------------------+----------------+------------------:
| 3 *678 -468 | 1579 79 179 | 489 2 1458 |
| 15 9 15 | 8 4 2 | 3 6 7 |
| *48 *78 2 | 1579 3 6 | 489 1458 1458 |
'---------------------'----------------'------------------'
Grouped AIC: 4 4- r4c3 -8- r46c2 =8= r79c2 -8- r9c1 -4 => r5c1,r7c3<>4
That is equivalent to my (and Leren's) Grouped W-Wing. If that chain is written in Eureka, it's exactly what Leren wrote.
For some reason I can't find the box 1 version under any name in Hodoku, but if it were there, it would be another Grouped AIC:
- Code: Select all
(4=8)r9c1 - r123c1 = r123c3 - (8=4)r4c3 => -4 r5c1,r7c3
(Hodoku would of course write it in its horrible Nice Loop notation.)
The same written in my abbreviated style:
- Code: Select all
(48)r9123c1 = (84)r1234c3 => -4 r5c1,r7c3
I suggest you study some fundamentals before claiming our namings are wrong. You can't rely on what some software tells you if you don't understand what it's actually telling you.
--
Edit. Added a correction based on new information.