|Subject:||Re: [Bug-gnubg] Bug in bearoffdump?|
|Date:||Sat, 31 Dec 2016 15:33:56 +0000|
Thanks! Out of interest, I was wondering if someone could give an example of a case where the 2 sided database would be different from the one-sided database? I had assumed that if you apply the database to both sides and have the full distribution, you could work out the optimal move just using this one-sided database?
From: Philippe Michel <address@hidden>
Sent: 31 December 2016 14:45
To: isambard mews
Subject: Re: [Bug-gnubg] Bug in bearoffdump?
On Tue, 27 Dec 2016, isambard mews wrote:
> I tested out bearoffdump on a test database using normal distribution
> format and got the following strange output (running on a 64bit Debian
> system). I was expecting a similar format to a non-ND database and
> wonder if this is a bug:
The problem is fixed in the current sources. If you use the debian package
I suppose you will have to wait until it is updated, but if you compiled
gnubg yourself you can update it from cvs or get the only changed file
|[Prev in Thread]||Current Thread||[Next in Thread]|