I guess the current top programs have much better playout policy than
the classical MoGo-style one.
The original policy of MoGo was,
(1) If the last move is an Atari, plays one saving move randomly.
(2) If there are "interesting" moves in the 8 positions around the
last move, plays one random
On Fri, 2008-01-04 at 16:50 -0800, steve uurtamo wrote:
> TCP/IP communication can be viewed as round-trip.
>
> UCP is one-way, TCP requires a response for each
> packet.
>
For a high-level protocol, it's all the same. The fact that a TCP/IP
packet is acknowledged matters not at all because the
s/UCP/UDP/g;
- Original Message
From: steve uurtamo <[EMAIL PROTECTED]>
To: computer-go
Sent: Friday, January 4, 2008 7:50:34 PM
Subject: Re: [computer-go] Please have your bot resign, for your own good
TCP/IP communication can be viewed as round-trip.
UCP is one-way, TCP requires a r
TCP/IP communication can be viewed as round-trip.
UCP is one-way, TCP requires a response for each
packet.
s.
- Original Message
From: Jason House <[EMAIL PROTECTED]>
To: computer-go
Sent: Friday, January 4, 2008 4:50:31 PM
Subject: Re: [computer-go] Please have your bot resign, for y
On Jan 4, 2008 4:44 PM, Gian-Carlo Pascutto <[EMAIL PROTECTED]> wrote:
> steve uurtamo wrote:
> >> It was my understanding that the netlag to the Philippines was about
> >> 380 ms; accounting for an additiaonal 15% packet loss and we end up
> >> at about 440 ms.
> >
> > i think that it works out t
steve uurtamo wrote:
It was my understanding that the netlag to the Philippines was about
380 ms; accounting for an additiaonal 15% packet loss and we end up
at about 440 ms.
i think that it works out to roughly double that because of the protocol, right?
Yes, the server sends out the move an
I altered the time gift for CGOS 9x9. I set it to 0.75 seconds.
In other words, the first 3/4 second of each move doesn't count against
your total time used.
- Don
___
computer-go mailing list
computer-go@computer-go.org
http://www.computer-go.or
> It was my understanding that the netlag to the Philippines was about
> 380 ms; accounting for an additiaonal 15% packet loss and we end up
> at about 440 ms.
i think that it works out to roughly double that because of the protocol, right?
s.
___
On Fri, 4 Jan 2008, Don Dailey wrote:
It was my understanding the bot was losing 2 seconds per move. 1/2
second would probably not fix this.
It was my understanding that the netlag to the Philippines was about
380 ms; accounting for an additiaonal 15% packet loss and we end up
at about 440 ms
It was my understanding the bot was losing 2 seconds per move. 1/2
second would probably not fix this.
- Don
Christoph Birk wrote:
> On Fri, 4 Jan 2008, Don Dailey wrote:
>> I think Fischer time is the solution to network lag. I can't give back
>> the lag time, but I can make it so that you
Hi Olivier,
Do you want me to send you the scripts?They are bash scripts and you
may have to slightly modify them.
- Don
Olivier Teytaud wrote:
>> Any progress on CGOS 19x19?
>>
>> It appears to have been stuck for 2 weeks now?
>
> Hum, I have not seen these emails before now;
> I launch th
I will ask Olivier if he wants my scripts.
- Don
Gian-Carlo Pascutto wrote:
> Chris Fant wrote:
>> CGOS 19 is has been stuck for a while now.
>>
>> At the bottom of the page, it says Many Faces is in a game, but does
>> not show it as currently playing at the top of the page. Perhaps the
>> p
[EMAIL PROTECTED] wrote:
> After 2000 playouts, AntIgo checks the estimated score. If it's way
> ahead, it stops thinking and just plays the best move it has so far.
> This way it plays very quickly when the game is won and the opponent
> does not resign. (I don't apply this rule in the beginning
I will ask Olivier if he wants to incorporate my scripts into the 19x19
server once I have it set up in cron.
The server is now hopefully working properly.
Don, I'll include your script soon; well, I hope so, when I have
a few minutes :-)
The trouble was reported with a title emphasizing the CGO
On Fri, 4 Jan 2008, Don Dailey wrote:
I think Fischer time is the solution to network lag. I can't give back
the lag time, but I can make it so that you should not lose games as a
result of it (unless it gets ridiculous.)
I don't object to Fisher Time but just increasing the move-credit
to 0.
Rémi Coulom wrote:
In Crazy Stone (maybe that is the case of MoGo, too), nakade is such a
big problem because the program avoids playing self-atari in playouts.
Crazy Stone will play the self-ataris anyway, but with a low
probability, so they are played at the end of the playout only. In case
Any progress on CGOS 19x19?
It appears to have been stuck for 2 weeks now?
Hum, I have not seen these emails before now;
I launch the Cgos19x19 right now, sorry for that.
I have received Don's email about the script, but
I do not use it yet. Minutes are very expensive :-)
Olivier
Chris Fant wrote:
CGOS 19 is has been stuck for a while now.
At the bottom of the page, it says Many Faces is in a game, but does
not show it as currently playing at the top of the page. Perhaps the
problem is related to a bot leaving near the time a round is
ending/beginning.
I guess Oliver i
After 2000 playouts, AntIgo checks the estimated score. If it's way ahead, it
stops thinking and just plays the best move it has so far. This way it plays
very quickly when the game is won and the opponent does not resign. (I don't
apply this rule in the beginning to avoid confusion in handicap
I think Fischer time is the solution to network lag. I can't give back
the lag time, but I can make it so that you should not lose games as a
result of it (unless it gets ridiculous.)
- Don
Jacques Basaldúa wrote:
> The problem is avoiding that an inferior program wins a lost position
> on tim
The problem is avoiding that an inferior program wins a lost position
on time extending the number of moves. If you could choose, what side
would you prefer to be? As a human, there is no doubt. But as a program
it is even better: the strongest program. Because computers can play faster
than human
The January 2008 KGS computer Go tournament will be this Sunday, January
6th, in the Asian night, European evening and American morning, starting
at 17:00 UTC (GMT) and ending about 21:00 UTC (GMT).
The Formal division will be an 8-round Swiss with 9x9 boards and 13
minutes each sudden death.
It might be possible to estimate lag by looking up the geographic location of a
bot's ISP. For instance via http://www.hostip.info/use.html .
Dave
Van: [EMAIL PROTECTED] namens Peter Christopher
Verzonden: vr 4-1-2008 5:27
Aan: computer-go@computer-go.org
Ond
23 matches
Mail list logo
