gnugo-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [gnugo-devel] influence and territory values


From: Gunnar Farnebäck
Subject: Re: [gnugo-devel] influence and territory values
Date: Sun, 14 May 2006 21:41:45 +0200
User-agent: EMH/1.14.1 SEMI/1.14.3 (Ushinoya) FLIM/1.14.2 (Yagi-Nishiguchi) APEL/10.3 Emacs/21.3 (sparc-sun-solaris2.9) MULE/5.0 (SAKAKI)

David wrote:
> >> Following from F6, option I is us G4, them C6, us D3, and option L is
> >> us D3, them C6, us G4.
> >>
> >> For option I: InfW=-7.00, TerrW=-3.00, InfB=-29.00, TerrB=-3.00
> >> For option L: InfW=-11.00, TerrW=-3.00, InfB=-31.00, TerrB=-3.00
> >>
> >> Why would the same board evaluate differently?
> >
> > No idea. How are InfW and InfB computed?
> 
> These are just short names for:
> 
>      influence4black = influence_score(INITIAL_INFLUENCE( BLACK ));
>      territory4black = influence_evaluate_position( BLACK, NULL,  
> &status );
>      influence4white = influence_score(INITIAL_INFLUENCE( WHITE ));
>      territory4white = influence_evaluate_position( WHITE, NULL,  
> &status );
> 
> calculated directly from the functions in engine/influence.c

If I understand things correctly, the GTP commands

boardsize 9
clear_board
play black f6
play white g4
play black c6
play white d3
initial_influence black territory_value
captures black
captures white

should show some difference compared to

boardsize 9
clear_board
play black f6
play white d3
play black c6
play white g4
initial_influence black territory_value
captures black
captures white

but I get identical results. Plausibly there could be some badly
initialized or reset data structure involved but then debugging would
require doing the same intermediate processing. In other words, in
order to get any further with this I would need complete and
preferrably minimal code to reproduce the problem.

/Gunnar




reply via email to

[Prev in Thread] Current Thread [Next in Thread]