Hi 999_Springs,
I'm breaking my pledge again, but I guess I may have to make an exception for this thread if the discussion continues.
999_Springs wrote:can someone enlighten me on why a forcing chain (whether it's an aic or not) would ever not be reversible?
I can't. That's what I've been saying. I can't think of a strictly unidirectional chain or a net of any kind. That's why most of the forcing chains/nets Hodoku finds are available as mirrored contradictions and verities. Not all, though, but I think this is the reason:
one could put a natural condition on the reversibility of a chain by disallowing any "or" statements in the chains and only allowing "and" statements (which is how SE organises its chain descriptions), which in this case would mean the second chain isn't reversible; or using only one "or" statement to be used at the beginning such as in kraken row/column/blocks with 3+ branches.
I guess such artificial restrictions are why Hodoku finds some nets as one or the other kind only, and why it doesn't find nets that require multi-krakens both ways at all. (Thank goodness,
totuan does!
).
but in some cases it can be clear and insightful to write chains with "or" statements in them which i can see in some of ttt/totuan's diagrams
like this one as well as some solutions in the daily puzzles that use the | symbol in chain notation which is a clever way to avoid writing branching in the chain
Exactly. As long as the ANDs and ORs are used properly, any chain or net is readable (and logically correct) both ways -- even things like memory chains, and probably even Denis' oriented chains (never tried but I see why not -- they look like memory chains to me).
Btw, did you see my
matrix translation of totuan's net? It also shows clearly the dual nature by splitting the net into two ORed sub-matrices (i.e. a block triangular matrix, BTM). Its correctness was confirmed by
Cenoman, and I'm pretty sure there's no simpler way to write it as a matrix. I conjecture that Hodoku only finds nets that can be written as a single triangular matrix (TM), which excludes nets with such unavoidable OR-branches. Here's another BTM I wrote for totuan's beautiful move
here:
- Code: Select all
*-----------------------------------------------------------------------------*
| 1347 1237 2347 | 34678 5 23468 | 2367 278 9 |
| 3457 2357 6 | 34789 34789 23489 | 1 2578 2358 |
| 357 8 9 | 1 367 236 | 23567 4 2356 |
|-------------------------+-------------------------+-------------------------|
| 2 1367 3478 | 34689 34689 5 | 4679 789 1468 |
| 45678 9 4578 | 468 1 468 | 24567 3 24568 |
| 134568 1356 3458 | 2 34689 7 | 4569 589 14568 |
|-------------------------+-------------------------+-------------------------|
| 3567 23567 1 | 345679 34679 3469 | 8 259 2345 |
| 3578 4 23578 | 35789 3789 1 | 2359 6 235 |
| 9 356 358 | 34568 2 3468 | 345 1 7 |
*-----------------------------------------------------------------------------*
Present as diagram: =>
r5c179<>6- Code: Select all
AALS(34578)r238c1 A*ALS(45678)r5c146
|| ||
(357)r238c1--(357=6)r7c1-----(6)r5c1
|| | ||
|| -----------------(57)r5c1
|| ||
|| (468)r5c146*
||
(4)r2c1-----(4)r2c5
|| | ||
|| | (4)r46c5-(4=68)r5c46*
|| | ||
|| | (4)r7c5----------(4)r7c9-----------------------------------
|| | || |
|| | AUR(48)r15c46 || |
|| | || || |
|| ----(4)r1c13 || |
|| || || |
|| (6)r5c46* || |
|| || || |
|| (8)r1c8----------(8)r2c9 A*ALS(24568)r5c146 |
|| | || || |
|| | (235)r278c9--(235=6)r3c9-(6)r5c9 |
|| | || | || |
|| | || -------------(25)r5c9 |
|| | || || |
|| | AALS(23458)r278c9 (468)r5c469* |
|| | |
(8)r8c1-----(8)r8c5 | (4)r7c5-----------------------------------
|| | ||
(8)r2c5----------(4)r2c5
|| ||
|| (4)r46c5-(4=68)r5c46*
||
(8)r46c5-(8=46)r5c46*
- Code: Select all
BTM 11x11 (sub-TMs: 7x7 + 7x7)
-----------------------------------------------------------------
6r5c46 48r5c46 :ALS (468)r5c46
4|8r5c1 5|6|7r5c1 :AAAALS (45678)r5c1
5673r2378c1 8r8c1 4r2c1 :AALS (345678)r2378c1
6r5c46 4r1c13 8r1c8 :UR (48)r15c46
4r46c5 4r2c5 4r7c5 :4C5
8r2c9 4r7c9 2356r2378c9 :AALS (234568)r2378c9
4|8r5c9 2|5|6r5c9 :AAAALS (24568)r5c9
==============================
8r46c5 8r8c5 8r2c5 :8C5
4r46c5 4r2c5 4r7c5 :4C5
8r2c9 4r7c9 2356r2378c9 :AALS (234568)r2378c9
4|8r5c9 2|5|6r5c9 :AAAALS (24568)r5c9
-----------------------------------------------------------------
-6r5c179
The matrix form turned out to be surprisingly simple (it's not quite one-to-one translation, but almost). If non-square matrices were accepted, it could even be compacted into an 8x9 BTM (harder to read, though):
- Code: Select all
-------------------------------------------------------------------------
6r5c46 48r5c46 :ALS (468)r5c46
4|8r5c1 5|6|7r5c1 :AAAALS (45678)r5c1
5673r2378c1 4r2c1 8r8c1 :AALS (345678)r2378c1
6r5c46 4r1c13 8r1c8 :UR (48)r15c46
8r46c5 8r8c5 8r2c5 :8C5
4r46c5 .4r2c5 .4r2c5 4r7c5 :4C5
.8r2c9 .8r2c9 4r7c9 2356r2378c9 :AALS (234568)r2378c9
4|8r5c9 2|5|6r5c9 :AAAALS (24568)r5c9
-------------------------------------------------------------------------
-6r5c179
Who would've thunk that, given the complexity of the move? (In this case there are many other reasons besides the BTM nature why Hodoku would never find such a move.)
space i disagree that this is unclear since the commas before "which" and after "direction" clearly indicate that it applies as a descriptor for all forcing chains. if the commas weren't there then it would be a specifier for one type of them. this is standard usage.
Is a non-native English speaker like myself or Robert supposed to know such a subtle detail? If I were using the Google translator, like Robert, I would get exactly the same translation with or without the comma -- and that translation would be ambiguous. That's not my excuse though.
I did see the comma and knew what it should mean, which is why I said that interpretation seemed more likely. However, I gave daVid the benefit of the doubt because I thought it was the worse possibility. I haven't seen anyone else define forcing chains to only include assumptive contradiction chains, and I don't think such a non-standard definition makes much sense anyway. So, maybe it was in fact unambiguously defined, but in that case I must repeat this part:
SpAce wrote:If you did in fact mean that all forcing chains are unidirectional and assumptive, then you were simply wrong (or using a very personal definition, which amounts to the same thing).
It's wrong also because no chain is truly unidirectional, as discussed above. If someone claims otherwise, they should provide a counter-example or define more clearly what they mean by "unidirectional".