Ticket #201 (new defect)
Inconsistent boundary values
| Reported by: | gunnar | Owned by: | gnugo |
|---|---|---|---|
| Priority: | normal | Milestone: | 3.9.x |
| Component: | source | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | patch: | yes |
Description
In the attached game at move 56,

















































































owl_defend F2 incorrectly finds an owl defense at F3, whereas owl_does_defend F3 F8 correctly says 0. However, when generating a move, owl_defend F2 precedes the owl_does_defend F3 F8 call and the latter finds a cached success result from the former search.
Tracking this down turns out to be a difference in owl boundary values, specifically for the J4 stone.
Attachments
Regression Results
| Attachment | Rev. | PASS | FAIL | Nodes | Status | |
| gunnar_7_12.11.diff | never tested |
Change History
Changed 4 years ago by gunnar
-
attachment
239160.sgf
added
Changed 4 years ago by gunnar
-
attachment
gunnar_7_12.11.diff
added
Mark both goal and boundary in sgf output of owl/semeai reading.
comment:1 Changed 4 years ago by gunnar
- patch set
The attached patch gunnar_7_12.11 adds better debugging support for the owl boundary, such that owl boundary value 1 is marked by a circle in the sgf files from owl/semeai reading and owl boundary value 2 is marked by a triangle. The goal is as before marked by an sgf "Mark".

Game record from CGOS.