bug-gnubg
[Top][All Lists]
Advanced

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

Re: [Bug-gnubg] Missed doubles problem ?


From: Joern Thyssen
Subject: Re: [Bug-gnubg] Missed doubles problem ?
Date: Thu, 4 Sep 2003 18:18:57 +0000
User-agent: Mutt/1.4.1i

On Thu, Sep 04, 2003 at 07:51:08PM +0200, Holger wrote
> >
> >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? 

Yes

> I think the doubling window should run from DP to TGP. 

True, but consider this simple example:

DP=50%
CP=70%
TG=90%

Using the average of DP and TG as originally suggested we would end up
using 70% as the divider -- that doesn't seem correct. I would call a
missed double at 71% a "missed double around the DP".

My new suggestion puts the divider at 80% which seems more correct in my
simple example above.

Alternatively, we can make three dividers:

Missed doubles around DP: 0% - 60%
Missed doubles around CP: 60% - 80%
Missed doubles around TG: 80%-100%

Perhaps that makes more sense.

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

No, you should compare the value with aarOutput[ 0 ][ OUTPUT_WIN ].

Jørn

Attachment: pgp_HYPyBPHcp.pgp
Description: PGP signature


reply via email to

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