eleven, related to your frequent complaints about the clarity of my chains, most recently
here, I'm interested in what you think of this "kraken":
Leren wrote:- Code: Select all
Kraken Column 9 Digit 2:
3r1c7 - 7r1c7 = (7-1) r1c1
3r1c7 - 7r1c7 = 7r1c1 - 7r7c1 = (7-1) r9c2 = 1r9c3 - 1r1c3 *= 1r1c9 - 2r1c9;
3r1c7 - 7r1c7 = 7r1c1 - (7=5) r7c1 - 5r3c1;
3r1c7 - 3r3c7 = (3-5) r3c3;
3r1c7 - 7r1c7 = 7r1c1 - (7=5) r7c1 - 5r9c23 = 5r9c8 - 5r3c8 *= 5r3c9 - 2r3c9; => - 3 r1c7; stte
No offense, Leren, but I think it's the ugliest mf I've seen in a long time
To be honest, I have much less interest in deciphering that than eleven's obfuscated C example which at least had the benefit of extreme brevity. Of course I can see how it works, but the way it's written and what it's called aren't in sync at all. It's a Nishio (contradiction net), not Kraken, and not intuitively followable even as such.
Since you're most likely generating your solutions with software in the first place, isn't it a piece of cake to change the way it outputs kraken solutions so they would have the normal left-to-right orientation? Of course, this last one would require quite a bit more than a simple reversal to make it readable, but at least it would fix the constant problem with your normal krakens. For special cases like this it shouldn't be too hard to put in some manual labor for the presentation.
Sorry about that, but I find it kind of funny that my chains are singled out as being "obfuscated"