diff --git a/docs/technical/kitscore.html b/docs/technical/kitscore.html new file mode 100644 index 000000000..cec896d00 --- /dev/null +++ b/docs/technical/kitscore.html @@ -0,0 +1,3177 @@ + + +
+ +A performance metric that makes sense. This metric can be applied to any game, virtual or real. Specific pieces of information relating directly to World of Tanks Blitz will be provided within parentheses and with a "WoTB:" prefix.
+KitScore is driven solely by the behavior of other players and finding meaning of a new observation within a pool of condensed data based on previously observed data. Generally, we will be provided with a number of statistics (the of an observation) per player (WoTB: , , , etc.) including a target statistic (the of an observation) that all other statistics try to maximize (WoTB: "winrate" which we will defined later as ).
+If the statistics are cumulative, they will have to be normalized (WoTB: statistics fetched from Wargaming are indeed cumulative even for a single player; , , , etc.). Each player will have such average statistics, giving us many points of data to work with. If the statistics are not cumulative, then you will be dealing with multiple observations per player which will only help improve accuracy.
+WN8, a widely adopted metric in the World of Tanks and World of Tanks Blitz communities is plagued with problems. One of them being that people often "what makes the metric tick." In other words, people easily exploit the rudimentary nature of WN8 to score undeservedly high.
+In WN8, the gains of some rewarding categories overshadow the losses of others. KitScore makes this nearly impossible as it punishes a player for scoring well solely high in a certain category. You will never exploit KitScore. Period.
+TODO: there's like no runaway cases
+| Symbol | +Interpretation | +
|---|---|
| + | The human readable version of the raw score . | +
| + | The raw KitScore. | +
| + | An arbitrary coefficient. | +
| + | The number of statistics including the target statistic. This means that there are entries for and entry for for each observation. | +
| + | The statistic index of where there are entries. | +
| + | A discriminator for the target statistic. There may never be more than entries for . | +
| + | The degree of the polynomial regression. | +
| + | The number of observations. | +
| + | An "atomic" score which is a function of the $i$th statistic. | +
| + | The weight of the $i$th atomic statistic. | +
The final metric is an arbitrarily scaled value of the raw score where is any coefficient of your liking. BlitzKit uses .
++
The final metric is the weighted average of individual scores which are functions of the $i$th statistic.
++
The "atomic" score is the difference between the predicted target statistic acquired using a polynomial regression of degree and the actual newly observed .
++
The polynomial regression of $m$th degree can be written as follows:
++
Polynomial regression coefficients can be acquired through basic linear algebra where an of constants is multiplied with of unknowns which equals another of constants.
++
The weight is a slice of the Pearson corelation matrix. The numerator is the corelation between the $i$th statistic and the target statistic while the denominator the sum of the corelations between the $i$th statistic and all statistics but the target statistic (including itself which will always result in ).
++
Some may find the weight equation arbitrary; it evidently isn't. The goal of is to eliminate over-rewarding the same behavior represented in multiple statistics. It makes all atomic statistics concurrent by leveraging the Pearson corelation matrix.
+A simplified example will clarify the idea. First, we compute a Pearson corelation matrix for statistics. We have and , the statistics that are trying to maximize . Reminder: a Pearson corelation matrix finds the value not only between and but also between all combinations of and themselves. Here, is calculated using polynomial regression corelation analysis to the $m$th degree.
+| + | + | + | + | + |
|---|---|---|---|---|
| + | + | + | + | + |
| + | + | + | + | + |
| + | + | + | + | + |
| + | + | + | + | + |
In the case above, meaning that both statistics have absolutely nothing to do with each other. Hence, the player will be awarded for optimizing both individually. And since , they should both be rewarded equally; in other words, they should have equal weights.
++
+
+
Now consider a case where and are fully correlated. It would be a bad idea to reward them equally; hence, their weights suffer.
+| + | + | + | + | + |
|---|---|---|---|---|
| + | + | + | + | + |
| + | + | + | + | + |
| + | + | + | + | + |
| + | + | + | + | + |
+
+
+