3-4-5 rule may result in a short-term gain, but will require refinement in due course to allow for what human players might call creativity.
Paul
Dec 30, 2008 11:56:58 PM, computer-go@computer-go.org wrote:
On Wed, Dec 31, 2008 at 12:25:10AM +0100, Rémi Coulom wrote:> > If you'd like to
cribed to some 10 lists,
also most [and by far] messages just get deleted instantly.)
Paul
___
computer-go mailing list
computer-go@computer-go.org
http://www.computer-go.org/mailman/listinfo/computer-go/
0 is
assumed by controllers and they may opt to never send commands
meant to be replied asynchronously.
Paul
___
computer-go mailing list
computer-go@computer-go.org
http://www.computer-go.org/mailman/listinfo/computer-go/
progress
It also makes sense to forbid an async_genmove (or simple genmove for
that matter) until the previous genmove/async_genmove has finished.
The engine should just fail with a predefined error string; I think
it is really cumbersome for the engine to try synchroniza
what about race conditions here? The engine may be responding to
> the async_genmove command an instant before it realizes an abort
> command
> just arrived. In this case it would be violating your rule but it
> wouldn't be anyone's fault.
There is no race condition bec
Don Dailey wrote:
> On Thu, 2007-03-08 at 12:27 -0500, Weston Markham wrote:
> > >
> > > There is no race condition because commands _are_ read
> > synchronously.
> > > But responses _may be_ sent asynchronously.
> > >
> > > Paul
> >
&g
where C is small.
However, this will tend to give you very artificial-looking positions.
Whether it is fine for your use-case, you know better.
[1] http://en.wikipedia.org/wiki/Rejection_sampling
Paul
___
computer-go mailing list
computer-go@co
