-
Notifications
You must be signed in to change notification settings - Fork 5
Expand file tree
/
Copy pathScoreExplanation.html
More file actions
61 lines (60 loc) · 2.57 KB
/
Copy pathScoreExplanation.html
File metadata and controls
61 lines (60 loc) · 2.57 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
<!DOCTYPE html><html><head><meta charset="utf-8"><title>LiteRumble - Scoring</title><link rel="stylesheet" type="text/css" media="all" href="style.css" /></head><body><h3><a href="/">LiteRumble</a> Scoring</h3>
<table>
<tr>
<th>Pairing Score</th>
<td>
This is calculated by the points that the bots got against each other, according to the formula:
<br>
botA_Score = 100*botA_Points/(botA_Points + botB_Points)
</td>
</tr>
<tr>
<th>Pairing Survival</th>
<td>This is calculated by the number of rounds that the bot survived the longest out of the total number of rounds, as a percentage. Formula:<br>
botA_Survival = 100*botA_rounds_won/game_total_rounds
</td>
</tr>
<tr>
<th>APS</th>
<td>
<b>A</b>verage <b>P</b>ercentage <b>S</b>core. <br>This is simply the average score across all bots/pairings.
</td>
</tr>
<tr>
<th>APS CI</th>
<td>
APS 95% <b>C</b>onfidence <b>I</b>nterval, from the spread of individual battle results. Shown as ± the half-width, so the APS is likely within this much of its true value. Each pairing needs at least 2 battles before it contributes; until then it shows n/a. Newly tracked pairings fill in gradually as more battles are uploaded.
</td>
</tr>
<tr>
<th>PWIN</th>
<td>
<b>P</b>ercentage <b>WIN</b>. <br>This is the percentage of competitors that the bot gets a score of over 50% against.
</td>
</tr>
<tr>
<th>NPP</th>
<td>
<b>N</b>ormalised <b>P</b>ercentage <b>P</b>air.<br>This is a normalised score against each competitor, with the highest score against them mapped to 100% and the lowest score against them mapped to 0%. If all are the same, everybody gets 100%.
</td>
</tr>
<tr>
<th>ANPP</th>
<td>
<b>A</b>verage <b>N</b>ormalised <b>P</b>ercentage <b>P</b>air. <br>The average NPP score against all enemies.
</td>
</tr>
<tr>
<th>Vote</th>
<td>
A point for every competitor that that the bot is the best against. Thus, each bot 'votes' for the competitor that they did worst against. This is then adjusted to a percentage of the number of bots in the rumble. Ties are divided between competitors.
</td>
</tr>
<tr>
<th>KNNPBI</th>
<td>
<b>K N</b>earest <b>N</b>eighbours <b>P</b>roblem <b>B</b>ot <b>I</b>ndex. <br>The average score of the K bots surrounding (ie. above and below) this bot in the ranking (according to APS) is subtracted from your score against each enemy. If the result is positive, it shows you that you do better than expected against this enemy. If negative, these are 'problem bots' which your competitors do better against than you do.
<br>K = ceil(sqrt(bots_in_rumble/2))
</table>
</body>
</html>