Difference between revisions of "Thread:Talk:RoboRumble/Participants/Is there a mistake in Rumble battle staging/reply"

Latest revision as of 05:57, 22 February 2023

What do you mean by avoiding particular bots. From the code, LiteRumble selects missing pairings first, then pairings with less battles, etc.

Given enough time, each bot should have similar amount of battles.

@@ Line 1: / Line 1: @@
 What do you mean by avoiding particular bots. From the [https://github.com/jkflying/literumble/blob/711a97db564d43789641a6ad33027f1da294d5d4/HandleQueuedResults.py#L452 code], LiteRumble selects missing pairings first, then pairings with less battles, etc.
 Given enough time, each bot should have similar amount of battles.
-Anyway, it's not a good idea to rely on LiteRumble to accurately measure how good each small change of your bot is. LiteRumble is designed to give everyone a ranking, well suited when you have a big change (proven to be effective) and want to publish the result. Small changes are prone to noises from the rumble environment (e.g. running on different computers for different versions, having updated opponents), thus may report unreliable result.
-Rumble clients are also much slower than running battles locally (with RoboRunner), due to added network communication (which isn't parallelized), as well as running battles from other updated bots. One can also notice that once each bot reaches ~5000 battles, most battles are then nano battles instead of randomly distributed across the entire rumble, due to some "propagation" effect, further slowing down the stabilization of the general rumble.