|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools | Rate Thread | Display Modes |
|
#16
|
||||
|
||||
|
Re: Compatition Ranking
Quote:
Last match of qualifications: Team A: Average Score:98pts/match Team B: 100pts/match Team C: 102pts/match Team D: 98pts/match Team E: 100pts/match Team F: 102pts/match Seems like a fair match-up right? but the stars align for team A-B-C and... Final score:A-B-C 300 | D-E-F 100 Even tough these teams were identical in their stats team A-B-C pulled out a significant win. The average scores of team D-E-F stay approximately the same, and while the teams were tied in the standings before this match took place teams A,B, and C are now all ahead of teams D,E, and F. My point being: since the same number of qualification matches are played (excluding surrogates) why does averaging matter? |
|
#17
|
|||
|
|||
|
Re: Compatition Ranking
Under this system of averaging, it is easier to compare between events that run different numbers of matches. This could be especially valuable if events within a single district region have to run different numbers of matches.
That's my guess anyway. |
|
#18
|
||||
|
||||
|
Re: Compatition Ranking
My updated insight is as follows- the averaging simply allows for an easier way to compare teams that have different number of matches played. For example:
Team A has a QA of 100pts/match and 4 games played Team B has a QA of 110pts/match and 3 games played This is a lot easier to compare than Team A has 400 points total, and 4 games played Team B has 330 points total, and 3 games played |
|
#19
|
||||
|
||||
|
Re: Compatition Ranking
The one nice (depending on your perspective) thing about the old method was more teams got to be in 1st place (or other high ranking spots) for a short while due to the extra noise. Now since everything is normalized, there will be a lot less movement in the rankings. A good thing from a usability standpoint, but not as many teams will get a short-lived boost from seeing their names at the top of the scrolling chart.
|
|
#20
|
|||||
|
|||||
|
Re: Compatition Ranking
My big question is if we are taking an AVERAGE score, then why leave out a surrogate match. Why not have that team's average be based on 11 matches instead of 10 (or whatever the case may be)? I can see in a Win/Loss scenario, or even if we were going with total points, but going off an average?
My fear is that teams will adopt the strategy of sabotaging their surrogate matches. If it doesn't count against them, why not lower the other teams' average? Granted, definitely NOT in the spirit of FIRST, but you know teams will do it. If we did away with surrogates this year, and let a few teams have an extra match figured into their average, I don't see where it would hurt. |
|
#21
|
|||||
|
|||||
|
Re: Compatition Ranking
My other question; Is ranking averaged match-by-match as the day goes on, or is it always calculated by the number of matches scheduled?
Example: After 3 matches, a team has 330 points. They are scheduled for 10 Qualifier matches. Is their current average 110 (330/3) or 33 (330/10)? |
|
#22
|
|||||
|
|||||
|
Re: Compatition Ranking
I Initially thought it was just to make the ranking nicer to watch, but it appears this doesn't happen...
Section 5.3.3: Quote:
This leads me to believe that the divisor of the average is constant through the whole event, actually making the whole averaging thing pointless for viewing purposes or... anything... over just a total. This seems really weird though, I'm guessing they don't mean that since, well, it doesn't make any sense. Last edited by dellagd : 05-01-2015 at 09:27. |
|
#23
|
||||
|
||||
|
Re: Compatition Ranking
Quote:
|
|
#24
|
||||
|
||||
|
Re: Compatition Ranking
I hope that District events stay with the standard 12 matches for all teams. This guarantees no surrogates and for smaller events also keeps a feasible inter-match minimum.
|
|
#25
|
||||
|
||||
|
Re: Compatition Ranking
Quote:
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|