Hi Nick, Some kind of limit on processing power would be interesting. To me it seems clear that a program like Zen benefits a lot by using more processing power than it's close competitors.
A measure that I find reasonable is a limit on number of threads x clock frequency. E.g., a program running on 64 intel cores, with 2 threads per core, at 3 Ghz would be counted as using 64x2x3 = 384 GHz, and a program running on 24 amd cores, with 1 thread per core, at 2.6 Ghz would be counted as 62.4 GHz. As long as the top just uses x86 type processors this should work reasonably well. For GPU's or ARM processors there probably needs to be a scaling factor. Another option could be to limit the power supply, e.g., you may not use more than say 400 Watt. BR, Erik PS As someone that participates only occasionally I like the zeros, but perhaps there is a friendlier way to indicate participation/absence. PS2 Crazy idea?: "Machine A plays black, machine B plays white. First player proposes the komi, the second player chooses the color&machine." On Wed, Oct 7, 2015 at 12:52 PM, Detlef Schmicker <d...@physik.de> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > Hi Nick, > > 3. would be great, I am very often going through round results to see > where CS or abakus has lost its games:) > > 1. I do not see a way to do this but running on same hardware (e.g. > Amazon EC2 with graphic card). Even this is unfair, as programs might > be optimized to other configurations (cluster) > > Detlef > > Am 07.10.2015 um 12:27 schrieb Nick Wedd: >> 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. >> >> >> >> _______________________________________________ Computer-go mailing >> list Computer-go@computer-go.org >> http://computer-go.org/mailman/listinfo/computer-go >> > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.22 (GNU/Linux) > > iQIcBAEBAgAGBQJWFPljAAoJEInWdHg+Znf4pMwQAI/4c2HhXA1DgAQEcOpulRAg > SSrDGCLyAypTQb3p1YDx45bvIIE9r0qBL+Ze+GRO/gD9peYmbayQWO7pQiL+2A/i > 2NSkr5gj6SR2JKW924Ba7NnBBIOil+bVX4Jku8PZJkz7MWwsP7LxFKhX2hA81Iis > EFdLAJ74atr7LSbERuhDYpwn/FcS9ag2h9k1zcwXD6R/OSuB46+OyR6dWw5NCrAL > FhjHo22rXig741ZTHtAxx7VXRwMdn6RV2oqkMbajFa7CLHFTcLRLMv3ix2TFyyd9 > JXwYKzJLxCeUNBWQ8WI5wvEqf7BPRjZcg0jujfR29zpg0AEooglrnnyIwRee9DPy > BGAxR8FmW/5kC1tygvM2c+shxvdhGrIB+1f8UoKIMp/IdhSLGuHc3Dq077+jCjG/ > QYA766C9tg+mqEPRp3nzqTP4G6cdTGlPfPLxMGGz6r1ltdlUwcqAy+Q/x6vztRJz > HH7ThXZgNpruhKqoDkltxW6udGpdeUiRW5u2JDCHVWPI6S+AjhdbtpI4EG+7Awwq > GUqk2LFlh3PItxl3UkYBpfevdHnUKXXG5UDxODEIQx43QgyYqLRjMsMXfaJGCbce > TBsJ9CvvyadAN2JhOzeIVRVZoWbzyk3t/+Pkyg4erhyi517jhmaXJApBQiKl1lOL > EqL1TfDx1ZJm+Ow0y18D > =JwJe > -----END PGP SIGNATURE----- > _______________________________________________ > Computer-go mailing list > Computer-go@computer-go.org > http://computer-go.org/mailman/listinfo/computer-go _______________________________________________ Computer-go mailing list Computer-go@computer-go.org http://computer-go.org/mailman/listinfo/computer-go
