1483 |
# CC5xx - experimental connection patterns |
# CC5xx - experimental connection patterns |
1484 |
# |
# |
1485 |
#################################################################### |
#################################################################### |
1486 |
|
# |
1487 |
|
# Note about patterns CC501, CC502, CC502b, CC511 |
1488 |
|
# |
1489 |
|
# In theory, these patterns go against the connection policy that the |
1490 |
|
# involved strings must be tactically stable (not capturable) and |
1491 |
|
# consequently, they should not be needed at all. In practice though, |
1492 |
|
# problems arise with the optics/owl analysis when such strings aren't |
1493 |
|
# amalgamated. An example (see owl:50) |
1494 |
|
# |
1495 |
|
# +------ |
1496 |
|
# |...X.O |
1497 |
|
# |XXX.XO |
1498 |
|
# |.OOXXO |
1499 |
|
# |O.OOOO |
1500 |
|
# |
1501 |
|
# In the absence of the mentioned patterns, the topmost X stone would |
1502 |
|
# NOT be amalgamated with the others, because all attempts at |
1503 |
|
# defending these kosumi connections result in a tactical capture of |
1504 |
|
# the whole string, thus a successful cut. |
1505 |
|
# |
1506 |
|
# As a consequence, the owl code would be run against separate targets, |
1507 |
|
# and in the above case, it would even fail to find a way to kill the |
1508 |
|
# topmost X stone (the lack of context is then responsible for the |
1509 |
|
# optics/owl code not being able to return vital points) |
1510 |
|
# |
1511 |
|
#################################################################### |
1512 |
|
|
1513 |
|
|
1514 |
Pattern CC501 |
Pattern CC501 |
1515 |
# Connect even if stones not tactically safe. |
# Connect even if stones not tactically safe. |