Gian-Carlo Pascutto wrote:
If it is indeed a KGS flaw I may add a workaround to Leela as simple
as doing time = time / 10 as soon as winrate >95% or so. There is
still a possibility of losing on time then but it should happen less.
That is almost the identical heuristic that Lazarus uses. But in
addition to this the time is loaded up front - in other words early
moves use a lot more time - but when win-rate is high it's divided by
something not quite as severe as 1/10 since it gradually plays faster
and faster based on the move number. I think it's a very good
algorithm. Lazarus also would speed up when losing badly just out
of good manners - unless resignation is turned on.
- Don
At the time when I was playing with my chess engine on the chess
servers, those servers provided "timeseal" and "timestamp" programs
that compensated for lag. It was no problem to play at timecontrols of
game in 1 minute with such tools, without any workarounds.
PS. I sent a correction to the hardware but I see the report still has
the old information. LeelaBot was on 1 x Intel Xeon 5355 @ 2.66Ghz, so
"only" 4 CPUs.
_______________________________________________
computer-go mailing list
computer-go@computer-go.org
http://www.computer-go.org/mailman/listinfo/computer-go/
