Nick & all, 1. Although introducing some limitation of cpu power is an intersting idea (actually my GPW Cup does), I think it's too early for KGS bot tournaments.
How to utilize computer clusters' power for planning tasks is a common and important reseach theme now. As communication over network is less effective than in-box one, playing-strength per (total) cpu-power get smaller when using computer clusters. Zen's root parallelization improves up-to 1 or 2 ranks but TDS based algorithms (used for Gommora and MP-Fuego) are expected to give more improvements. Preventing such effort must be a bad idea, I strongly believe. So, at least, a simple sum of cpu power of all node computers is not acceptable. (Some discouting could be?) Cpu power of each SMP or NUMA box can be computed by number-of-(physical-)cores times clock-frequency (although Erik used logical-cores). Using number-of-threads instead might be better. For more fairness, some factors can be defined for processor arichitectures or manufacturers, because some participants have to use non-Intel processors due to their environments. For GPUs, I have no concrete idea now. Simple flops is not enough and more discussion is necessary, I believe. Another idea, you (or we?) can define some benchmark program(s). 2. I don't understand this at all. It's just a record of fact. Intentional omitting of information must be a bad idea. 3. Watching the crosstable in real-time should be a fan for all observers. Hideki Nick Wedd: <caevtg+nheacva2ibm6h-ulxg-9indqsgzfquj7jfdp6rv1o...@mail.gmail.com>: >I am thinking of making some small changes to the way I run bot tournaments >on KGS. If you have ever taken part in a KGS bot tournament, I would like >to hear your opinions on three things. > > >1. Limit on processor power? > >This is the main point on which I want your opinions. The other two are >trivial. > >Several people have suggested to me that these events would be fairer if >there were a limit on the computing power of the entrants. I would like to >do this, but I don't know how. I have little understanding of the >terminology, I don't know how *e.g.* multiple cores in one computer compare >with multiple computers on one network, and I don't know how to count a >graphics card. *If* someone can find a way to specify an upper limit to >permitted power which is clear and easy to understand, and *if* most >entrants would favor imposing such a limit, I will discuss what it should >be, and apply it. I am not able to check what entrants are really running >on, but I will trust people. > > >2. Zeroes in the "Annual Championship" table. > >The table at http://www.weddslist.com/kgs/annual/index.html has a 0 in a >cell where a program competed but did not score, and a blank where it did >not compete (at least it should do, I sometimes get it wrong). I would >prefer to omit these zeroes, they seem a bit rude. Also there is no clear >distinction between competing and not competing - how should I treat a >program which crashes and disappears after two rounds, or one (like AyaMC >last Sunday) which plays in every round but is broken and has no chance of >winning? I realise that the zeroes some convey information that may be of >interest. Should I continue to use them, or just leave those cells blank? > > >3. Live crosstable > >When I write up my reports, I include a crosstable, like the one near the >top of http://www.weddslist.com/kgs/past/116/index.html . This is easy for >me, I run a script which reads the data from the KGS page ( >http://www.gokgs.com/tournEntrants.jsp?sort=s&id=990 in this case) and >builds the crosstable in html, which I copy into the tournament report. It >only works for Swiss (and maybe Round Robin) tournaments. It works while >the tournament is still running, though only between rounds.I could build a >current crosstable each round during a tournament if there is any demand >for it. -- Hideki Kato <mailto:hideki_ka...@ybb.ne.jp> _______________________________________________ Computer-go mailing list Computer-go@computer-go.org http://computer-go.org/mailman/listinfo/computer-go
