usually computer go tournaments are non byo yomi tournaments. However, it is useful to have byo yomi in gtp to interface programs with IGS or NNGS, and with graphical front ends.. I agree that we should let room for any time system to be supported. In the get_clock command, how do we know if we are in byo yomi or in the main time, and how do we know there is no byo yomi ?
I think this would need some changes. This will only support Canadian byo-yomi and non-byo-yomi tournaments. We should make sure that any clock protocol supports other time systems and it should be easy to add new time systems later. So I'd recommend:
set_clock <time system> <parameters>
I think the following time systems would cover all common Go clocks: * set_clock none * set_clock absolute <time> * set_clock canadian <time> <byoyomi time> <byoyomi stones> * set_clock japanese <time> <byoyomi time> <byoyomi periods> * set_clock ing <time> <byoyomi time> <byoyomi cost> [<byoyomi time 2> <byoyomi cost 2> [...]] That should do it. We could probably even leave Ing out - in my experience, even tournaments run by the Ing foundation don't often use the Ing "pay points for more time" system.
On Fri, 2001-12-07 at 03:01, Tanguy Urvoy wrote: Most computer tournaments include a time constraint I suggest 3 new GTP commands:
set_clock <main time> <byoyomi time> <byoyomi stones> get_clock_time <color> get_clock_stones <color>
gtp mailing list gtp@lists.lysator.liu.se http://lists.lysator.liu.se/mailman/listinfo/gtp