keith wrote:- Code: Select all
|1257 237 8 |1257 1267 4 |3679 39 26 |
----------------------------------------------------------
|6 12 259 |124 1234 1235 |8 29 7 |
|3 1278 27 |1278 9 1278 |46 5 46 |
|25789 278 4 |2578 2378 6 |39 239 1 |
----------------------------------------------------------
The UR / AUR <39> is in R69C78. The fifth cell is R7C8, <29>. My elimination would be R6C7 is not <3>. Myth Jellies pointed out the strong link on <9> in R6: R9C8 is not <9>.
It took me awhile to see that 9 elimination, but wow, what a great deduction!
RW wrote:According to your candidate grid there would also be a strong link on <3> in box 9 and you could eliminate '3' from r6c7 without the fifth cell.
There doesn't appear to be a strong link on 3 in box 9(the lower right hand one right?).
keith wrote:My claim: I have seen many examples of overlapping XY-wings, in which the reductions of one XY-wing destroy the other wings and their reductions. Sequence matters.
I wouldn't think that sequence should matter. As long as an elimination is valid, it shouldn't matter when you do it. If you identify 2 xy-wings and one destroys the other, the conclusions of both should still be valid. An xy-wing is an xy-wing. I have another claim: The deduction from any solving method should be valid even if it uses 'destroyed' candidates. Now I may be jumping the gun on this, but it's just a gut feeling. We use incorrect candidates in chains all the time. In essence those candidates are not really there, so eliminating one may 'destroy' the loop, but just write it back in and the loop is there. Is there some proven rule that loops only work after all possible simpler reductions have been made... singles, pairs, etc? Hell, I think you should be able to use solved cells in loops, just write in some candidates, but this would probably not be fruitful.
Could you post an example of overlapping xy-wings where one destoys the other and its conclusions? I would be really curious to look into that.