![]() |
High level scoring analysis 2012-2014
1 Attachment(s)
After reading much discussion about matches "decided by fouls" in the 2014 game, I wondered how the overall percentage of such games compared with past years. I found one early season report of "about 10%", and a few more detailed analyses. While I'm sure the latter contain the information, I wasn't up to going through the trees to find the forest I was looking for, so I wrote the attached program, with the results below. I defined a "decisive" scoring component (autonomous, teleoperated, endgame, or foul points) as one which would have changed the match outcome (won/lost/tied) had it been zero. Percentages are the percentage of matches for which each scoring component met this criterion. Matches where the individual components failed to add up to the total for either team were ignored.
Qualification matches: Code:
> java -Dtype=Q CSVStats *csvCode:
> java -Dtype=E CSVStats *csvCode:
> java CSVStats *csv |
Re: High level scoring analysis 2012-2014
So, the good news is that with the combined 2014 stats, 101% of points were scored without fouls, so folks should not be complaining..... Unfortunately for the refs, teams were giving 114% effort on average.
|
Re: High level scoring analysis 2012-2014
Quote:
|
Re: High level scoring analysis 2012-2014
Quote:
|
Re: High level scoring analysis 2012-2014
It's amazing how balanced these percentages are for the 2012 eliminations.
|
Re: High level scoring analysis 2012-2014
I'm not sure IKE was really serious, but as others have observed, the numbers don't have to add to 100%, and only would if every match had exactly one "decisive" factor. Many have more than one, e.g. a 40-35 match where the winner had 10/10/10/10, and many don't have any, e.g. a 40-20 match with the same breakdown.
Other definitions of "decisive" are possible, which is why for quantitative analysis it's important to pick one and be clear about what it is. Another interesting distinction is between a decisive factor and the decisive factor. The same data can be sliced and diced many ways, one of which is to count matches decided by exactly one distinct scoring category. I did a bunch of that and won't bore you with it; for the most part it shows the same general characteristics with different numbers. One might be worth noting though: Foul points "a deciding factor" (as in the earlier tables) Code:
Matches PercentageCode:
Matches PercentageIMO, this is a measurable factor that goes a long way toward explaining some of the intense dislike of this game. Having matches decided by factors that involve necessarily inconsistent and often inscrutable human judgement calls is what's called in the world of quality analysis a "dissatisfier" - something that causes dissatisfaction (no matter what the product's other good qualities) if got wrong, though no one ever compliments anyone for getting it right. No, not all foul points are questionable or hard to accept, but in the aggregate they're a good proxy measurement for the rate of occurrence of ones that are. Again IMO, I'll propose that the cold hard percentage rate of "matches decided by foul points" (either one, computed in this or a similar way of your choice) is a useful inverse "figure of merit" for a game. Keeping it low should be an explicit game design goal in the future. |
Re: High level scoring analysis 2012-2014
Thank you for this. It is nice to see some objective analyse of the foul problems this year.
What I would be really interested to see is how this breaks down by week. |
Re: High level scoring analysis 2012-2014
Quote:
Week6: http://www.chiefdelphi.com/media/papers/2995 Week7: http://www.chiefdelphi.com/media/papers/3000 Archimedes Curie Galileo Newton: http://www.chiefdelphi.com/media/papers/3018 If there's interest I can run the script for weeks 1 through 4 individually. |
| All times are GMT -5. The time now is 10:28. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi