[Top][All Lists]

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

Re: [Bug-gnubg] Missed doubles problem ?

From: Holger
Subject: Re: [Bug-gnubg] Missed doubles problem ?
Date: Thu, 04 Sep 2003 19:51:08 +0200

At 19:03 01.09.2003 +0000, Joern Thyssen wrote:
On Mon, Sep 01, 2003 at 01:13:55AM +0200, Holger wrote
> At 21:44 29.08.03 +0000, Joern Thyssen wrote:
> >However, there is still the point about modifying the logic to use DP
> >and TG instead of the crude "<= 0.95" logic.
> I'm on my way to implement this.
> Looking at the market window MaX's DP is 50,7% (for dead cube), but when
> opp. redoubles it's 81,4% (which gnubg will do if it takes because score is
> 2-away - 4-away)
> TGP is 88,9%.
> This leads to:
> DP1: 50,7% < Middle1: 69,8% < NoD: 82,6% < DPass: 83,0% < DTake: 85,2% <
> TGP: 88,9%
> DP2: 81,4% < NoD: 82,6% < DPass: 83,0% < Middle2: 85,15% < DTake: 85,2% <
> TGP: 88,9%
> Unfortunately, I still don't know enough bg theory. So what I'm not sure
> about is which window to take to compute its middle and after I know the
> middle, which cube action to compare it with.

Hmm, good question.

Instead of the average of the DP and the TG point, it makes more sense
to consider the average of the CP and the TG point. As you note we
should use the live cube values, e.g., the bottom line.

Are you sure you mean CP? I think the doubling window should run from DP to TGP. If I understood it well, those points can vary according to cube availability. I'll have to look how this is determined. Maybe I can always use aaarPointsMatch[ player ][ point_type ][ 1 ].

And the other question: right now I'm comparing the middle of the doubling window to the no-double equity. I'm not sure whether this is correct. (In case you answered this one, I didn't take the answer to be for that question.)



reply via email to

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