blue wrote:Intresting situation.
I wonder if the reversal would slip by without notice:
(5)r7c5 = (597)r764c1 - (7=5)r4c4
Not past me (probably)
The mistake might be slightly harder to notice because the chain is more natural to read that way, but obviously it's still there because the reversal doesn't really change anything. In both cases the intended logic is easy to deduce by looking at the full chain and the grid, but as per AIC rules, every link must work independently and that doesn't happen here.
The strong link (5)r7c5 = (597)r764c1 is valid, but the (unordered) locked set (597)r764c1 doesn't imply a locked 7r4c1 (7 can be in r6c1 as well) which is required for the weak link with 7r4c4. Thus, even though we know how the digits will be distributed because of the preceding strong link, the weak link (597)r764c1 - (7)r4c3 is not valid when viewed in isolation. The dreaded comma (implying an ordered tuple) is needed:
(5)r7c5 = (5,9,7)r764c1 - (7=5)r4c3
Now the 7r4c1 is fixed, as it should be for the weak link to work. That works just as well in the original orientation:
(5=7)r4c3 - (7,9,5)r467c1 = (5)r7c5
In other words, now the weak link is between 7r4c3 and that particular distribution of those digits in those cells, which is valid and enough for our purposes. The weak link between 7r4c3 and the full unordered (579)r467c1 locked set is not valid, however, because 7r4c3 doesn't forbid the distribution (5,7,9)r467c1.
If nuances like that are hard to grasp, which I fully understand, I would strongly recommend sticking to the long form:
Ngisa wrote:Well, I just wanted to shorten the chain:
(5=7)r4c4 - (7)r4c1 = (7-9)r6c1 = (9-5)r7c1 = (5)r7c5 =>....
That is fully correct, of course. It can also be shortened without resorting to the comma:
(5=7)r4c3 - (79)r46c1 = (95)r7c15 => ...
This would also work:
(5,7)r4c41 = (79-5)r67c1 = (5)r7c5 => ...