Ticket #201 (new defect)

Opened 4 months ago

Last modified 4 months ago

Inconsistent boundary values

Reported by: gunnar Assigned to: gnugo
Priority: normal Milestone: 3.8
Component: source Version:
Severity: normal Keywords:
Cc: patch: 1

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

239160.sgf (1.4 kB) - added by gunnar on 01/01/08 17:30:06.
Game record from CGOS.
gunnar_7_12.11.diff (2.6 kB) - added by gunnar on 01/01/08 17:36:02.
Mark both goal and boundary in sgf output of owl/semeai reading.

Change History

01/01/08 17:30:06 changed by gunnar

  • attachment 239160.sgf added.

Game record from CGOS.

01/01/08 17:36:02 changed by gunnar

  • attachment gunnar_7_12.11.diff added.

Mark both goal and boundary in sgf output of owl/semeai reading.

01/01/08 17:38:39 changed by gunnar

  • patch set to 1.

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".