[Withdrawn: I keep trying to treat networks and chains differently, but there's an overlap of chains into networks that trips me up all too often.]
_
ronk wrote:(7=56)r38c7 - (6)r3c4=(16)r3c4,r2c5 - (61=351)r6c5,r4c45 - (15=7)r4c3 => -7 r4c7 ; stte
daj95376 wrote:An alternate perspective:
- Code: Select all
(57=6)r38c7 - (6=1)r3c4 - (1=5)r4c4 \
- (1=6)r2c5 - (56=3)r6c5 - r4c5 = 3r4c7 => -57 r4c7
_
Or ... [(157)r4c345=3r4c5 - 3r6c5=XYWing(156)r34c4,r6c5 - (6=1)r2c5 - (1=6)r3c4 - (6=57)r38c6] - (57=3)r4c4; stteSteveG48 wrote:
- Code: Select all
*--------------------------------------------------------------------*
| 6 59 8 | 3 7 4 | 1 59 2 |
| 4 179 179 | 2 b16 5 | 6789 789 3 |
| 3 2 157 |b16 9 8 |a567 4 57 |
*----------------------+----------------------+----------------------|
| 9 8 d157 |c15 c135 2 | 35-7 6 4 |
| 17 1567 3 | 14568 1456 9 | 2 578 578 |
| 2 4 56 | 568 c356 7 | 358 1 9 |
*----------------------+----------------------+----------------------|
| 17 1379 1479 | 45 2 6 | 5789 35789 578 |
| 8 67 467 | 9 45 3 |a57 2 1 |
| 5 39 2 | 7 8 1 | 4 39 6 |
*--------------------------------------------------------------------*
(7=56)r38c7 - (6=16)b2p57 - (16=315)b5p128 - (15=7)r4c3 => -7 r4c7 ; stte
David P Bird wrote:ronk wrote:(7=56)r38c7 - (6)r3c4=(16)r3c4,r2c5 - (61=351)r6c5,r4c45 - (15=7)r4c3 => -7 r4c7 ; stte
For example, is (61=351)r6c5,r4c45 a sound strong link? If (6)r6c5 is false the first term is false but it won't force the required distribution of digits in the second term. The same points arise if the link is taken in the reverse direction.
David P Bird wrote:Ronk, so you're resorting to using split nodes! But I think that it should be spelled out that listing gives the digits and cells they occupy in order.
+-----------------+-----------------+-------------------+
| 6 59 8 | 3 7 4 | 1 59 2 |
| 4 179 179 | 2 (16) 5 | 6789 789 3 |
| 3 2 157 | (16) 9 8 | (567) 4 57 |
+-----------------+-----------------+-------------------+
| 9 8 (157) | (15) (135) 2 | 3-57 6 4 |
| 17 1567 3 | 14568 1456 9 | 2 578 578 |
| 2 4 56 | 568 (356) 7 | 358 1 9 |
+-----------------+-----------------+-------------------+
| 17 1379 1479 | 45 2 6 | 5789 35789 578 |
| 8 67 467 | 9 45 3 | (57) 2 1 |
| 5 39 2 | 7 8 1 | 4 39 6 |
+-----------------+-----------------+-------------------+
3r6c5 - (3=157)r4c345 ----------------------- 57r4c7
||
5r6c5 - (5=1)r4c4 - (1=6)r3c4 - (6=57)r38c7 - 57r4c7
||
6r6c5 - (6=1)r2c5 - (1=6)r3c4 - (6=57)r38c7 - 57r4c7
3r6c5 - (3=157)r4c345 ------------------------- 57r4c7
||
5r6c5 - (5=1)r4c4 --- (1=6)r3c4 - (6=57)r38c7 - 57r4c7
|| /
6r6c5 - (6=1)r2c5 -
daj95376 wrote:SteveG48 wrote:daj95376 wrote:An alternate perspective:
- Code: Select all
(57=6)r38c7 - (6=1)r3c4 - (1=5)r4c4 \
- (1=6)r2c5 - (56=3)r6c5 - r4c5 = 3r4c7 => -57 r4c7
_
OK, why not modify your alternative from
(56=3)r6c5 - r4c5 = 3r4c7 => -57 r4c7
to
(56=3)r6c5 - (3=15)r4c45 - (15=7)r4c3 etc. ?
You know how the law says that you can't be tried twice for the same crime? Well, your scenario assigns <5> twice to the same cell.
It's already assigned by (1=5)r4c4, you can't assign it again by performing: (3=15)r4c45.
blue wrote:
- Code: Select all
+-----------------+-----------------+-------------------+
| 6 59 8 | 3 7 4 | 1 59 2 |
| 4 179 179 | 2 (16) 5 | 6789 789 3 |
| 3 2 157 | (16) 9 8 | (567) 4 57 |
+-----------------+-----------------+-------------------+
| 9 8 (157) | (15) (135) 2 | 3-57 6 4 |
| 17 1567 3 | 14568 1456 9 | 2 578 578 |
| 2 4 56 | 568 (356) 7 | 358 1 9 |
+-----------------+-----------------+-------------------+
| 17 1379 1479 | 45 2 6 | 5789 35789 578 |
| 8 67 467 | 9 45 3 | (57) 2 1 |
| 5 39 2 | 7 8 1 | 4 39 6 |
+-----------------+-----------------+-------------------+
This similar, but not identical to JC's alternate desctription of Steve's elimination:
(157=3)r4c345 - 3r6c5 = [XY-Wing: pivot=r6c5,pincers=r2c5,r3c4] - (1=6)r3c4 - (6=57)r38c7 => -57r4c7
David P Bird wrote:Playing with JC's and Blue's approach (well done!) I get this split node chain
(7=153)r3c345 - (3=56#1)r6c5 - (56=1#1)r4c4,r2c5 - (1=6)r3c4 - (6=57)r38c7 => r4c7 <> 7
The key point here is that in the blue node (1) only needs to be true or false in one of the cells to propagate the chain in either direction so I believe that this is a valid AIC.
David P Bird wrote:PS I see you've posted an alternative chain while I've been writing, but you've cheated and used a completely different set of cells!