David P Bird wrote:I don't see any other possibility that having a candidate locked in the object pair to form an AHS
Look at ronk's extreme example < here >. There is an Almost Hidden Set (578+x)r2358c7. The object cell pair r34c7 must contain a base digit (1234) and a digit locked in the hidden set (578) so (69) can be eliminated from these cells.
With my illustration as it stands, I have to agree with champagne. It should be OK after removing base candidates in the added AAHS cells (r58c5 and r5c8 of the exemplar). This will at least guarantee a base candidate exists in each "object pair."
I don't recall examples for either of the two following illustrations. Examples would be appreciated. [edit: daj95376 and champagne, that means each of you for your own illustration.]
daj95376 wrote:Note: there is a rare scenario that DPB's scenarios don't cover. (the distinction between QExocet and JExocet.)
- Code: Select all
"Q" is forced to contain the candidate
*-------*-------*-------*
| B B - | - - - | - - - |
| - - - | Q / / | R . . |
| - - - | Q / / | R . . |
*-------*-------*-------*
| . . S | S . . | S . . |
| . . S | S . . | S . . |
| . . S | S . . | S . . |
*-------*-------*-------*
| . . S | S . . | S . . |
| . . S | S . . | S . . |
| . . S | S . . | S . . |
*-------*-------*-------*
champagne wrote: ... a last tentative contribution to your jexocet definition.
- Code: Select all
*-------*-------*-------*
| B B - | - - - | - - - |
| - - - | Q . . | R . . |
| - - - | Q . . | R . . |
*-------*-------*-------*
| . . 0 | . . . | . . . |
| . . . | 0 . . | 0 . . |
| . . . | . . . |. . . |
*-------*-------*-------*
| . . . | . . . | . . . |
| . . 0 |. . . | . . . |
| . . 0 | . . . | . . . |
*-------*-------*-------*
in such a situation, the jexocet is established.
champagne wrote:David P Bird wrote:
- Code: Select all
v v v
r4 . . \ | \ . . | \ . . . . O | \ . . | O . . . . \ | \ . . | O . .
r5 . . O | O . . | O . . < . . O | \ . . | O . . . . O | O . . | O . . <
r6 . . \ | \ . . | \ . . . . O | \ . . | O . . . . \ | \ . . | O . .
r7 . . \ | \ . . | \ . . . . O | \ . . | O . . . . \ | \ . . | O . .
r8 . . O | O . . | O . . < . . O | \ . . | O . . . . \ | \ . . | O . .
r9 . . \ | \ . . | \ . . . . O | \ . . | O . . . . \ | \ . . | O . .
2 Parallel Lines(I) 2 Parallel Lines(II) 2 Orthogonal Lines
rows 5 & 8 columns 3 & 7 row 5 & column 7
I have difficulties with these diagrams.
First one is ok,
In the second and third one, I can't see the possibility to have so many occurrences of the digit.
I don't see clearly the case where the cross line in stack 1 is empty and Q;R is forced in stacks 2 and 3.
Good luck with that! I brought up the same point in mid-April and it met the fate of a proverbial lead balloon. Perhaps illustrations with a separate "don't care" symbol, say "x", would have flown better.
- Code: Select all
v v v
r4 . . \ | \ . . | \ . . . . x | \ . . | x . . . . \ | \ . . | x . .
r5 . . O | O . . | O . . < . . x | \ . . | x . . . . O | O . . | x . . <
r6 . . \ | \ . . | \ . . . . x | \ . . | x . . . . \ | \ . . | x . .
r7 . . \ | \ . . | \ . . . . x | \ . . | x . . . . \ | \ . . | x . .
r8 . . O | O . . | O . . < . . x | \ . . | x . . . . \ | \ . . | x . .
r9 . . \ | \ . . | \ . . . . x | \ . . | x . . . . \ | \ . . | x . .
'x' <-> presence or absence of candidate 'O' is irrelevant