Ticket #113 (new defect)

Opened 6 years ago

Last modified 3 years ago

Making a seki

Reported by: sanxiyn Owned by: gnugo
Priority: normal Milestone: 3.9.x
Component: source Version:
Severity: normal Keywords:
Cc: patch: no

Description (last modified by sanxiyn) (diff)

Simplified from a real game. White can turn the corner into a seki, but GNU Go finds out only after the exchange.

Try:

gnugo -l seki.sgf -L 1
gnugo -l seki.sgf -L 3

Attachments

seki.sgf Download (146 bytes) - added by sanxiyn 6 years ago.

Regression Results

Attachment Rev. PASS FAIL Nodes Status

Change History

Changed 6 years ago by sanxiyn

comment:1 Changed 6 years ago by sanxiyn

  • Description modified (diff)

comment:2 Changed 6 years ago by gunnar

This a known weakness in the semeai analysis, which can only work on pre-existing stones. Solving it would involve rewriting owl_analyze_semeai_after_move() so it can handle one of the dragons being the just played stone, writing an autohelper to verify whether playing a stone would result in seki, adding some patterns to indicate where it would be worthwhile trying to get a seki, and finding out how to compute the value of the move to make seki.

Some standard seki shapes, e.g. the one in seki:101,











are already detected but only by using very explicit patterns like S3 at source:patterns/patterns.db@2339#L13472.

comment:3 Changed 3 years ago by gunnar

  • Milestone changed from 3.8 to 3.9.x

The semeai analysis has improved significantly with respect to my previous comment since then. The attached position would probably still fail but it should at least be added as a testcase.

Note: See TracTickets for help on using tickets.