|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
| Thread Tools | Rate Thread | Display Modes |
|
#16
|
||||
|
||||
|
Re: Upset Percentage
Here is a spreadsheet I made for English class with all the upsets from the past 4 years: https://docs.google.com/spreadsheets...it?usp=sharing
|
|
#17
|
||||
|
||||
|
Re: Upset Percentage
Something I think a lot of teams did across the board for champs that might not be ideal was scouting defense crossings and using that to help calculate overall scores for robots. We opted to not even scout crossings since the breach is guaranteed at the championships level. That being said I wish we did scout crossings just so we can compare what our overall scores list would look like when comparing crossings vs without crossing. I would imagine teams that focus more on poaching the enemies secret passage would move up in our scouting ranking vs teams that cycle.
|
|
#18
|
|||||
|
|||||
|
Re: Upset Percentage
Quote:
|
|
#19
|
||||
|
||||
|
Re: Upset Percentage
Looks like your right. Thanks for point that out! I'll update it right now.
|
|
#20
|
|||||
|
|||||
|
Re: Upset Percentage
Quote:
|
|
#21
|
||||
|
||||
|
Re: Upset Percentage
Quote:
|
|
#22
|
|||||
|
|||||
|
Re: Upset Percentage
There are only 2^7=128 possible elim outcomes. TBA lists 142 events in 2016 alone. It's likely to happen at some frequency.
|
|
#23
|
|||
|
|||
|
Re: Upset Percentage
Handy table for the odds of a perfect reverse bracket
50% odds of underdog winning-->Once every 128 tournaments 45% --> once every 268 tournaments (roughly 2 years) 40% --> once every 610 tournaments (roughly 4 years) 35% --> once every 1554 tournaments (roughly 10 years) 30% --> once every 4572 tournaments (roughly 30 years) 25% --> once every 16,384 tournaments (roughly 100 years) 20% --> once every 78,125 tournaments (roughly 600 years) |
|
#24
|
||||
|
||||
|
Re: Upset Percentage
Quote:
Code:
select matches.event, events.name, match_levels.name, matches.set_number, matches.match_number, red_scores.total_points as red_points, blue_scores.total_points as blue_points from matches inner join events on matches.event = events.id inner join match_levels on matches.match_level = match_levels.id inner join match_scores as red_scores on matches.id = red_scores.match inner join match_scores as blue_scores on matches.id = blue_scores.match where match_level > 1 and red_scores.alliance_color = "red" and blue_scores.alliance_color = "blue" and blue_points > red_points and events.is_official = 1 order by matches.event Edit 2: I added some logic to figure out upsets that were tie scores. That added 7 total upsets. 32%. Interestingly, 4322 won an upset on a tie at OCR QF2-1. That match now shows in the results. Code:
and (blue_points > red_points or (blue_points = red_points and blue_scores.foul_points > red_scores.foul_points)) Last edited by markmcgary : 05-11-2016 at 07:13 PM. Reason: Added upsets from ties. |
|
#25
|
|||
|
|||
|
Re: Upset Percentage
Quote:
<http://www.thebluealliance.com/match/2016pncmp_f1m1> we were on the red alliance even though we were the #5 alliance going against the #2 alliance. |
|
#26
|
||||
|
||||
|
Re: Upset Percentage
That could certainly impact the results. I thought that red was always the higher seeded alliance and alliances sometimes change bumper colors during playoffs to maintain that relationship. I'd have to study the database design more deeply to determine the relationships between the matches, alliances and their seeding. I took the easy way assuming (incorrectly?) that blue was always the lower seed. The SQL will get more ugly. I wonder how significant will be the impact on the percentage?
|
|
#27
|
||||
|
||||
|
Re: Upset Percentage
Quote:
|
|
#28
|
|||||
|
|||||
|
Re: Upset Percentage
Quote:
Thus, #1 is always red. #8 is blue, but can take over red if they beat #1. #2 is red, unless they're in finals; #7 is blue unless they beat #2. #3 is red against #6, and blue otherwise (#6 is always blue). #4 is red against #5, blue for semis, and red for finals (while #5 is blue unless they're in finals). Or, to put it another way: Alliance: QFs, SFs, Fs (assuming they make it that far) #1: R, R, R #2: R, R, B #3: R, B, B #4: R, B, R #5: B, B, R #6: B, B, B #7: B, R, B #8: B, R, R Best reason to be on the #1 alliance, you don't change your bumper color. (OK, so #6 has the same perk...) |
|
#29
|
||||
|
||||
|
Re: Upset Percentage
Some robots just look better in blue anyways.
|
|
#30
|
|||
|
|||
|
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|