Re: [gnugo-devel] Readconnect

[Arend Bayer]

I'll add s.th. to readconnect's future jobs, as this is a problem one
encounters tuning the influence module that my approach certainly cannot
overcome. 

On Sun, 9 Dec 2001, Gunnar Farneback wrote:

> 1. Revise induce_secondary_move_reasons() to make use of readconnect.
> This should make the code simpler and more robust.
> 
> 2. Replace all B and C patterns in patterns.db and patterns2.db with a
> new module, possibly pattern driven, which uses readconnect to find
> connecting and cutting moves.

2.a. Replace at least some of the barrier patterns for the influence by
some intelligent integration of connection analysis. That should be used
both to spread the influence more accurately, and to generate moves that
protect border or our/break into the opponent's territory.

> 
> 3. Throw out the amalgamation code and replace it by something based
> on readconnect. This would involve replacing find_connections() and
> find_cuts() but more important is to take down the automatic
> amalgamation around eyespaces.
>
> 4. Replace jump_out_helper and similar with readconnect based
> conditions. In general many patterns which require a safe move would
> be better served with a "can connect" kind of constraint.
> 
> 5. Revise the owl reading to make use of readconnect.
> 

Arend