RoboRunner/Version History - Revision history

Voidious: RoboRunner 1.2.3 - fix team battles

2012-09-30T19:26:20Z

RoboRunner 1.2.3 - fix team battles

Voidious: capitalization

2012-08-23T04:09:47Z

capitalization

Voidious: RoboRunner 1.2.2 - fix bug with multiple of same bot in a bot list

2012-08-23T03:58:11Z

RoboRunner 1.2.2 - fix bug with multiple of same bot in a bot list

Voidious: adjust wording of confidence accuracy guarantees

2012-08-15T13:43:19Z

adjust wording of confidence accuracy guarantees

Voidious: fix formula

2012-08-15T03:08:41Z

fix formula

Voidious: RoboRunner 1.2.1 - confidence interval on overall score

2012-08-15T01:39:59Z

RoboRunner 1.2.1 - confidence interval on overall score

Voidious at 15:24, 13 August 2012

2012-08-13T15:24:20Z

Voidious: forgot: displays confidence intervals

2012-08-13T14:59:46Z

forgot: displays confidence intervals

Voidious: fix random battle chance

2012-08-13T01:56:50Z

fix random battle chance

Voidious: RoboRunner 1.2.0 - smart battle selection

2012-08-13T01:43:03Z

RoboRunner 1.2.0 - smart battle selection

@@ Line 6: / Line 6: @@
 }}
 ----
 * 1.2.2 - 8/22/2012
 ** Correctly handle multiple of the same bot in a single battle.

@@ Line 8: / Line 8: @@
 * 1.2.2 - 8/22/2012
 ** Correctly handle multiple of the same bot in a single battle.
-** When using smart battle selection, Increase the initial chance of a random battle from 2% to 10%.
+** When using smart battle selection, increase the initial chance of a random battle from 2% to 10%.
 * 1.2.1 - 8/14/2012
 ** Display approximate 95% confidence interval for overall score. Uses a faster/less accurate version when showing overall score between battles (I've seen a range of ~.02), with a more thorough calculation in the final score (should be accurate to 2 decimal places).

@@ Line 6: / Line 6: @@
 }}
 ----
 * 1.2.1 - 8/14/2012
 ** Display approximate 95% confidence interval for overall score. Uses a faster/less accurate version when showing overall score between battles (I've seen a range of ~.02), with a more thorough calculation in the final score (should be accurate to 2 decimal places).

@@ Line 7: / Line 7: @@
 ----
 * 1.2.1 - 8/14/2012
-** Display approximate 95% confidence interval for overall score. Uses a faster/less accurate version (accurate to a range of ~.02) when showing overall score between battles, with a more thorough calculation in the final score (accurate to 2 decimal places).
+** Display approximate 95% confidence interval for overall score. Uses a faster/less accurate version when showing overall score between battles (I've seen a range of ~.02), with a more thorough calculation in the final score (should be accurate to 2 decimal places).
 * 1.2.0 - 8/12/2012
 ** Change data file format to use gzipped XML files with raw scores for every individual battle. Data files are about the same size as before (but only because they are zipped).

@@ Line 13: / Line 13: @@
 ** Add -smart argument to enable smart battle selection. After running 2 battles against each bot (or set of bots), tries to select the battle that will increase the overall score accuracy in the least amount of time.
 *** It calculates the expected decrease in the [[wikipedia:Standard error|standard error]] that the next battle would provide, divided by the average running time for that battle.
-*** I.e.: <math>{{SE \over \sqrt{numBattles}} - {SE \over \sqrt{numBattles + 1}}} \over {avgBattleTime}</math>
+*** I.e.: <math>{{SD \over \sqrt{numBattles}} - {SD \over \sqrt{numBattles + 1}}} \over {avgBattleTime}</math>
 *** If number of bots is > number of threads, only one instance of a battle configuration is scheduled at a time.
 *** A small number of random battles are sprinkled in from among the bots with the fewest battles, to mitigate situations where the variance after 2 battles was randomly low or zero. Probability of running a random battle is: <math>.02 \over 2 ^ {minBattles - 2}</math>, and the battle is randomly chosen from the bots tied for the fewest battles. I'll make this more configurable if/when anyone cares.
@@ Line 24: / Line 24: @@
 ** Support bot groups in challenges. If present, group scores will be printed and overall score will be average of group scores.
 ** Print wiki formatted scores for [[Targeting Challenge]] (BULLET_DAMAGE) or [[Movement Challenge|Movement Challenge]] (MOVEMENT_CHALLENGE) scoring styles.
-** Print scores against each bot/set of bots and overall score after all battles are run. Run with 0 seasons to see challenge scores.
+** Print scores against each bot/set of bots and overall score after all battles are run. Run with 0 seasons to see overall scores.
 * 1.1.0 - 7/28/2012
 ** Support for all basic scoring options: percent score, survival firsts, survival score, bullet damage (TC), and movement challenge.

@@ Line 12: / Line 12: @@
 *** I.e.: <math>{{SE \over \sqrt{numBattles}} - {SE \over \sqrt{numBattles + 1}}} \over {avgBattleTime}</math>
 *** If number of bots is > number of threads, only one instance of a battle configuration is scheduled at a time.
-*** A small number of random battles are sprinkled in from among the bots with the fewest battles, to mitigate situations where the variance after 2 battles was randomly low or zero. Probability of running a random battle is: <math>.02 * 2 ^ {minBattles - 2}</math>, and the battle is randomly chosen from the bots tied for the fewest battles. I'll make this more configurable if/when anyone cares.
+*** A small number of random battles are sprinkled in from among the bots with the fewest battles, to mitigate situations where the variance after 2 battles was randomly low or zero. Probability of running a random battle is: <math>.02 \over 2 ^ {minBattles - 2}</math>, and the battle is randomly chosen from the bots tied for the fewest battles. I'll make this more configurable if/when anyone cares.
 * 1.1.2 - 8/5/2012
 ** Add -t argument to set number of threads, up to number of Robocode installs configured in roborunner.properties.