It might be possible to automatically compensate for lag by looking up the geographic location of a bot's ISP. For instance via http://www.hostip.info/use.html <https://webmail.planet.nl/exchweb/bin/redir.asp?URL=http://www.hostip.info/use.html> . Dave
________________________________ Van: [EMAIL PROTECTED] namens Peter Christopher Verzonden: za 5-1-2008 12:25 Aan: computer-go@computer-go.org Onderwerp: [computer-go] update on networking from phils with new CGOSconfiguration Strangely enough, today the network from the phils to boardspace.net is so bad that even don's new configuration doesn't make up for the additional network lag (though I think it alleviates the bot's pain). With .2 seconds of thinking time, the net time "detracted" from time_remaining is still decreasing an average of 1 sec per move. I did run this same bot from a friend's server @ the same configuration, .2 sec/move, and the bot always still has 300 seconds remaining after every move [ a .7s/move bot ALSO always still had 300 seconds], so this means that Don's change works & no problem in CGOS in general, the problem is the network from the philippines. Strangely, my ping from the philippines to boardspace.net at the time of this testing is 700ms. BUT my ping from the philippines to MIT.edu is only 350ms. So, I thought, "Maybe boardspace.net has a network problem." I tested from the server in the US. ping to boardspace.net -> 20ms. ping to mit.edu -> 12ms. I definitely cannot understand those results. For the present time, it appears I may have to throw in the towel on getting dependable results running the bots from my laptop in the philippines. Raw output of ping & cgos script follows. Peter ps I did notice Fat1800 resign a lost game against my bot from my laptop in the phils, thanks ;-) Now, if my bot could only achieve winning positions against Fat1800 on a regular basis ;) -----------------PING FROM PHILIPPINES -------------------------------- 0 [EMAIL PROTECTED] ping mit.edu PING mit.edu (18.7.22.69) 56(84) bytes of data. 64 bytes from WEB.MIT.EDU (18.7.22.69): icmp_seq=1 ttl=238 time=354 ms 64 bytes from WEB.MIT.EDU (18.7.22.69): icmp_seq=2 ttl=238 time=354 ms 64 bytes from WEB.MIT.EDU (18.7.22.69): icmp_seq=3 ttl=238 time=363 ms 64 bytes from WEB.MIT.EDU (18.7.22.69): icmp_seq=4 ttl=238 time=371 ms 64 bytes from WEB.MIT.EDU (18.7.22.69): icmp_seq=5 ttl=238 time=346 ms 64 bytes from WEB.MIT.EDU (18.7.22.69): icmp_seq=6 ttl=238 time=355 ms 64 bytes from WEB.MIT.EDU (18.7.22.69): icmp_seq=7 ttl=238 time=330 ms 64 bytes from WEB.MIT.EDU (18.7.22.69): icmp_seq=8 ttl=238 time=338 ms --- mit.edu ping statistics --- 8 packets transmitted, 8 received, 0% packet loss, time 7086ms rtt min/avg/max/mdev = 330.218/351.896/371.914/12.419 ms 0 [EMAIL PROTECTED] ping 208.100.19.102 [boardspace.net] PING 208.100.19.102 (208.100.19.102) 56(84) bytes of data. 64 bytes from 208.100.19.102: icmp_seq=1 ttl=49 time=615 ms 64 bytes from 208.100.19.102: icmp_seq=2 ttl=49 time=668 ms 64 bytes from 208.100.19.102: icmp_seq=3 ttl=49 time=761 ms 64 bytes from 208.100.19.102: icmp_seq=4 ttl=49 time=651 ms 64 bytes from 208.100.19.102: icmp_seq=5 ttl=49 time=740 ms --- 208.100.19.102 ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4026ms rtt min/avg/max/mdev = 615.330/687.537/761.351/55.010 ms ----------------------PING FROM AMAZON EC2 -------------------------- 127 [EMAIL PROTECTED] ping boardspace.net PING boardspace.net (208.100.19.102) 56(84) bytes of data. 64 bytes from boardspace.net (208.100.19.102): icmp_seq=1 ttl=50 time=20.6 ms 64 bytes from boardspace.net (208.100.19.102): icmp_seq=2 ttl=50 time=20.6 ms 64 bytes from boardspace.net (208.100.19.102): icmp_seq=3 ttl=50 time=20.7 ms 64 bytes from boardspace.net (208.100.19.102): icmp_seq=4 ttl=50 time=20.9 ms 64 bytes from boardspace.net (208.100.19.102): icmp_seq=5 ttl=50 time=20.9 ms --- boardspace.net ping statistics --- 5 packets transmitted, 5 received, 0% packet loss, time 4003ms rtt min/avg/max/mdev = 20.622/20.782/20.960/0.228 ms 0 [EMAIL PROTECTED] ping mit.edu PING mit.edu (18.7.22.69) 56(84) bytes of data. 64 bytes from WEB.MIT.EDU (18.7.22.69): icmp_seq=1 ttl=239 time=12.1 ms 64 bytes from WEB.MIT.EDU (18.7.22.69): icmp_seq=2 ttl=239 time=12.4 ms 64 bytes from WEB.MIT.EDU (18.7.22.69): icmp_seq=3 ttl=239 time=12.4 ms 64 bytes from WEB.MIT.EDU (18.7.22.69): icmp_seq=4 ttl=239 time=12.9 ms --- mit.edu ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 2997ms rtt min/avg/max/mdev = 12.171/12.511/12.929/0.292 ms ----------------------------------------------------------------------------- Output from philippines of .2 sec / move bot with cgos script 18:51:55 S->C genmove b 300000 18:51:55 C->E time_left b 300 0 18:51:55 E->C = 18:51:55 C->E genmove b 18:51:55 E->C = G2 18:51:55 C->S G2 18:52:10 S->C info Estimated time until next round: 09:56 18:52:10 Estimated time until next round: 09:56 18:52:12 S->C play w F6 284916 18:52:12 C->E play w F6 18:52:12 E->C = 18:52:12 S->C genmove b 299823 18:52:12 C->E time_left b 299 0 18:52:12 E->C = 18:52:12 C->E genmove b 18:52:13 E->C = D8 18:52:13 C->S D8 18:52:25 S->C info Estimated time until next round: 09:56 18:52:25 Estimated time until next round: 09:56 18:52:28 S->C play w G4 271014 18:52:28 C->E play w G4 18:52:28 E->C = 18:52:29 S->C genmove b 298950 18:52:29 C->E time_left b 298 0 18:52:29 E->C = 18:52:29 C->E genmove b 18:52:29 E->C = J4 18:52:29 C->S J4 18:52:40 S->C info Estimated time until next round: 09:23 18:52:40 Estimated time until next round: 09:23 18:52:44 S->C play w D5 257472 18:52:44 C->E play w D5 18:52:44 E->C = 18:52:45 S->C genmove b 298171 18:52:45 C->E time_left b 298 0 18:52:45 E->C = 18:52:45 C->E genmove b 18:52:45 E->C = D4 18:52:45 C->S D4 18:52:55 S->C info Estimated time until next round: 09:13 18:52:55 Estimated time until next round: 09:13 18:53:00 S->C play w E4 244298 18:53:00 C->E play w E4 18:53:00 E->C = 18:53:00 S->C genmove b 297107 18:53:00 C->E time_left b 297 0 18:53:00 E->C = 18:53:00 C->E genmove b 18:53:01 E->C = D3 18:53:01 C->S D3 18:53:10 S->C info Estimated time until next round: 09:03 18:53:10 Estimated time until next round: 09:03 18:53:15 S->C play w E7 231787 18:53:15 C->E play w E7 18:53:15 E->C = 18:53:15 S->C genmove b 296079 18:53:15 C->E time_left b 296 0 18:53:15 E->C = 18:53:15 C->E genmove b 18:53:16 E->C = E8 18:53:16 C->S E8 18:53:25 S->C info Estimated time until next round: 08:52 18:53:25 Estimated time until next round: 08:52 18:53:29 S->C play w C5 219696 18:53:29 C->E play w C5 18:53:29 E->C = 18:53:30 S->C genmove b 295098 18:53:30 C->E time_left b 295 0 18:53:30 E->C = 18:53:30 C->E genmove b 18:53:30 E->C = C6 18:53:30 C->S C6 18:53:40 S->C info Estimated time until next round: 08:42 18:53:40 Estimated time until next round: 08:42 18:53:43 S->C play w D7 208308 18:53:43 C->E play w D7 18:53:43 E->C = 18:53:44 S->C genmove b 294101 18:53:44 C->E time_left b 294 0 _______________________________________________ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/
_______________________________________________ computer-go mailing list computer-go@computer-go.org http://www.computer-go.org/mailman/listinfo/computer-go/
