[net.games.go] go clocks with byo-yomi?

mlj@mtfmc.UUCP (M.JULIAR) (09/10/85)

Does anybody know of a clock that can keep time for a go game the
way a chess clock does for chess?  Such a clock, however, must allow
for byo-yomi (is that the correct term?).

Unlike clocking in chess, go gives a player, whose time has run out,
a short period of time to make each additional play.  For instance,
if each player in a match is allowed one hour, then byo-yomi might
be 15 seconds for each move after normal time.

I understand that in professional matches in Asia, the timekeeper
counts down the byo-yomi out loud so that each player knows exactly 
how many seconds are left.  It sounds very nerve racking.

I assume such a go clock would more easily be made if it were
electronic and digital.  It shouldn't be difficult to write a little
program on your PC to do the job.  But I don't carry my PC around
with me wherever I play go.  So, I wonder if there is a
battery-operated one available?

andrew@stc.UUCP (Andrew Macpherson) (09/16/85)

In article <474@mtfmc.UUCP> mlj@mtfmc.UUCP (M.JULIAR) writes:
>Does anybody know of a clock that can keep time for a go game the
>way a chess clock does for chess?  Such a clock, however, must allow
>for byo-yomi (is that the correct term?).
Yes, the term I mean.
>
>I understand that in professional matches in Asia, the timekeeper
>counts down the byo-yomi out loud so that each player knows exactly 
>how many seconds are left.  It sounds very nerve racking.

This dosn't solve your problem.  Here in the UK we usually grab someone
who has completed his match to count byo-yomi, in your example 10, 5,
4, 3, 2, 1, PASS.  Timekeepers word is final.  Of course for the basic
game it is a case of chess clocks.

It is nerve wracking for the one in time trouble, but then it is meant
to be.

On a related subject, is there any sort of standard for byo-yomi?  I
have played in games where it has been as high as 20sec, and as short
as 5.  I am inclined to believe that the 5sec limit is more
appropriate.
-- 
Regards,
	Andrew Macpherson.	<andrew@stc.UUCP>
	{creed, datlog, idec, iclbra, iclkid, root44, stl, ukc}!stc!andrew