|
From: | Holger |
Subject: | Re: [Bug-gnubg] Missed doubles problem ? |
Date: | Thu, 04 Sep 2003 21:38:26 +0200 |
At 19:21 04.09.2003 +0000, Joern Thyssen wrote:
On Thu, Sep 04, 2003 at 09:15:58PM +0200, Holger wrote > > >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. > > This I like much more. If you don't mind I'll implement this. No problem, but you have to add a few more elements to statcontext.
Hmm, why is that? I planned to return a 2-value-array from getMarketWindowDividerMWC(). In there I should be able to compute both dividers easily. And then I just compare aarOutput[ 0 ][ OUTPUT_WIN ] like below.
> >No, you should compare the value with aarOutput[ 0 ][ OUTPUT_WIN ]. > > Just to confirm whether I understood: aarOutput[ 0 ][ OUTPUT_WIN ] should > equal arDouble[ OUTPUT_OPTIMAL ] ? No, the aaarPoints array contains the game winning chance at the various points, so the test should be something like:
No, you misunderstood. Sorry for not being clear. I didn't mean what I have to compare. I was just asking whether the statement above is true. I figured out the logic below from your last mail.
rDPDivider = ... rCPDivider = ... if ( aarOutput[ 0 ][ OUTPUT_WIN ] <= rDPDivider ) /* missed double around DP */ ... else if ( aarOutput[ 0 ][ OUTPUT_WIN ] <= rCPDivider ) /* missed double around CP */ ... else /* missed double around TG */ and same logic for wrong doubles.
Regards,Holger
[Prev in Thread] | Current Thread | [Next in Thread] |