storm_norm wrote:The trick is to notice what looks like a UR, but really can't take advantage of the common rules of URs to make any eliminations. AND its very important that the UR candidates are the ONLY candidates left in the floor cells. as in this grid
- Code: Select all
+--------+-----------+-------+
| 12 . . | 12345 . . | . . . |
| . . . | . . . | . . . |
| 12 . . | 12345 . . | . . . |
+--------+-----------+-------+
| . . . | . . . | . . . |
| . . . | 13 . . | . . . |
| . . . | 25 . . | . . . |
+--------+-----------+-------+
| . . . | . . . | . . . |
| . . . | . . . | . . . |
| . . . | . . . | . . . |
+--------+-----------+-------+
it just so happens that there is another 1 and another 2 in column 4. both cannot be false at the same time (that will force the UR to exist, NO NO !!) This provides yet another strong inference to exploit
UR12[(1)r5c4 = (2)r6c4]
Are we to assume the bivalues contain the only other UR digits in column 4?
storm_norm wrote:consider this grid and notice the UR {1,2} in r46c14
- Code: Select all
+--------+-------------+-------+
| . . . | 3456789 . . | . . . |
| . . . | 3456789 . . | . . . |
| . . . | 12(3456). . | . . . |
+--------+-------------+-------+
| 12 . . | 12345 . . | . . . |
| . . . | . . . | . . . |
| 12 . . | 12345 . . | . . . |
+--------+-------------+-------+
| . . . | 3456789 . . | . . . |
| . . . | 3456789 . . | . . . |
| . . . | 3456789 . . | . . . |
+--------+-------------+-------+
as stated before, the extra UR candidates 1 and 2 in r3c4 exist in the same cell. From the rules of URs we can now eliminate the {3,4,5,6} from r3c4 because neither the 1 nor the 2 can be false at the same time.
Are we to assume r3c4 contains the only other UR digits in column 4? IOW what about r5c4?