Hi tarek,
tarek wrote:?3-Turbot Crane (using 2 grouped strong links)
That's an interesting Grouped L1-Wing, but I don't see any resemblance to a Turbot Crane! I think the defining feature of the Crane is the EmR type of box-link, and we don't have that here. In fact, I don't see much resemblance to any Turbot Fish type, but the least of all the Crane. The elimination logic here is actually most similar to a Skyscraper (line & box covers). Thus, if anything, I think that's a very twisted Skyscraper.
That said, I'm not sure if it's a great idea to even try to name patterns like this after Turbot Fishes. Turbots are well-defined and easily recognized in their original two-strong-link forms, but extending that naming to more links has a strong potential to hurt more than help, I'm afraid. I think any named patterns should be so simple and well-defined that there's absolutely no confusion. For anything beyond that the more generic parent type is better. In this case Grouped L1-Wing/X-Chain would work, or Finned Franken Swordfish.
r57b1\c13b7 fins r13c3
Slightly simpler: r57b1\c134 f:r7c2; or avoiding the fin issue: (1)R57B1\c14[c3b7]
Btw, I think you should add the fish digit to the fish notation. I hate reading fishes where I have to look around for the actual digit, like in all the old fish discussions!! Not having a standard for that was a mistake in the UFG, I think.
With this one r7c1 is double covered which makes it a potential cannibalistic elimination
But only potential because it would need a third cover to get actually eliminated.
In sukaku explainer cannibalistic EE are not yet supported nor are endofins …
This would mean losing out on some useful (albeit more complicated) pattern eliminations. This may be something I can add as an option in the future
Cannibalism usually implies that simpler options exist, and endofins can usually be avoided too. So, I don't think it's missing out on much.