Ticket #107 (closed task: fixed)
eyes.db improvements
| Reported by: | gunnar | Owned by: | gunnar |
|---|---|---|---|
| Priority: | normal | Milestone: | 3.9.1 |
| Component: | source | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | patch: | yes |
Description
The encoding of eye values in GNU Go includes a number of different stable eyes, where one or both players can threaten to decrease or increase the number of eyes (eye values 0001 0002 0111 0112 1112 0222 1222). These are used in eyes.db but certainly not everywhere they occur and more importantly the points where threats can be made are not marked. See #101 for an example where it would be useful to have threat points marked, in that case the eye pattern
(.( :0001
The key to doing this with reasonable efficiency is the GTP function analyze_eyegraph (functionality implemented at the end of source:engine/optics.c) and automating calling it for different configurations of margins and opponent stones for a given eyeshape.
Attachments
Regression Results
| Attachment | Rev. | PASS | FAIL | Nodes | Status | |
| gunnar_7_13.3.diff | never tested | |||||
| gunnar_7_13.5.diff | 2428 | 1 | 1 | +0.14% +0.41% +0.039% | details | |
| 2431 | 1 | 1 | +0.13% +0.4% +0.029% | details | ||
| 2435 | 1 | 1 | +0.13% +0.4% +0.028% | details | ||
| gunnar_7_13.5b.diff | 2446 | 2 | +0.14% +0.4% +0.031% | details | ||
| gunnar_7_9.14.diff | 2381 | 0% 0% 0% | details | |||
| gunnar_7_9.14b.diff | 2381 | 0% 0% 0% | details |

