Hi
tarek and
rjamil,
tarek wrote:Regrading L1 & grouped strong link in box,
I hope that you agree with me this:
- Code: Select all
+++++++++
| X X X |
| X X X |
| . . . |
+++++++++
Would constitute a grouped strong link in box different from that of an Empty rectangle.
Good point! I'm glad you brought this up because boxes can indeed host two kinds of grouped links! In this first example the strong link is between two mini-rows (could be two mini-cols) within the box. Since they're group nodes, it's a grouped link. If the same is a simple link (between just two candidates) then it can be seen as either a line-based (in this case column) or a box-based bilocation strong link, but the grouped link is obviously box-based only. (Btw, Franken Fishes have these kinds of box formations.)
An example:
- Code: Select all
-1 -1 -1 | . 12 . | 2 2 2
. . . | . . . | / / /
. 12 . |-1 -1 -1 | 2 2 2
--------+---------+--------
Grouped W-Wing: (1=2)r3c2 - r3c789 = r1c789 - (2=1)r1c5 => -1 r1c123,r3c456
On the other hand, in an ER the strong link is between a mini-row and a mini-col, so it's clearly different (like a hinge). It's still a grouped link because it's between group nodes as well (unless it has just two candidates). Thus I would call such a pattern "grouped" too. However, I have nothing against it if someone wants to distinguish between the two different types of box links otherwise, but "grouped" is equally applicable to both kinds anyway. "Grouped" simply means that a link is between more than two candidates, and I would attach that qualifier to any pattern that uses at least one such link. (Btw, Mutant Fishes have these hinge types of box formations.)
An example:
- Code: Select all
. . . | . . . | / 2 /
. 12 . | . . . | 2 2-1 2
. . . | . . . | / 2 /
--------+---------+----------
. . . | . . . | . . .
. -1 . | . . . | . 12 .
. . . | . . . | . . .
Grouped W-Wing: (1=2)r2c2 - r2c789 = r13c8 - (2=1)r5c8 => -1 r2c8,r5c2
If it's important to distinguish the two kinds of group links, I guess one could add another qualifier like "hinge" to the latter case, as in "Grouped (hinge) W-Wing". Personally I think the "Grouped" qualifier is more important and enough.
Whereas the ER would give something like this:
- Code: Select all
+++++++++
| . X . |
| X . . |
| . . . |
+++++++++
Yes. Unlike the other simplified link, the "reduced" ER link is always box-only. I think
StrmCkr's term for it is actually Minimal ER (unless it's changed lately). That link (or a pattern using it) would not be "grouped" because it only has two candidates. It's also a bit different from the grouped ER, because it can function in several different ways. The weak links of a grouped ER are fully defined as a single row and a single column, so it's easy to see as a well-defined strong hinge, but a minimal ER is more ambiguous as either candidate can link to both rows and columns. Its hinge gets fully defined only when used within a larger pattern. In fact, it doesn't have to be a hinge at all, as it can function like the first pattern too!
rjamil wrote:Reduced Empty Rectangle = Turbot Crane
Empty Rectangle = Grouped Turbot Crane
I agree with that, especially if Reduced -> Minimal (I think). Naturally I would strongly prefer the right-hand terms.
tarek wrote:I am of the view that we need to move away from the Empty rectangle term because to me & some other players it is a type of grouped strong link in a box (I demonstrated a 3 strong link pattern composed only of Empty rectangles). Some other players use the term Empty rectangle to signify a 2 strong link pattern (or a grouped Turbot crane)
I wouldn't mind that. Like I've said before, Empty Rectangle is a horribly ambiguous term. However, it's also used very much so it might be difficult to change. But, it would be a good start if we could at least rename the simplest ER patterns as Turbot Crane and Grouped Turbot Crane. That would make me very happy!
Personally I would prefer "hinge" as a generic term to describe any orthogonal box-link (strong or weak). So, how about "strong hinge" and "weak hinge" to describe those box links? I think that would be very unambiguous!
The Turbot Fish family has examples of both: Turbot Crane has a strong hinge and 2-String Kite has a weak hinge, and that's true whether they're grouped or not. Because it's an invariant of those patterns, we can safely use the "Grouped" prefix with them because it tells exactly where the group nodes must be. A Grouped Crane has a "grouped strong hinge" while a Grouped Kite has a "grouped weak hinge" (and one or two grouped line-based strong links). A Grouped Skyscraper obviously has a single line-based grouped strong link. Thus there's zero ambiguity when using the "Grouped" prefix with Turbot Fishes. It just makes it easier to identify the pattern in the grid, knowing it's a bit more complex than the simple case.