|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools |
Rating:
|
Display Modes |
|
|
|
#1
|
||||
|
||||
|
[EWCP] Presents TwentyFour -- An FRC Statistics Blog
As mentioned in the State of EWCPcast, we think that there is a huge amount of data floating around that most teams aren’t using to design better robots. We’ve decided to “do the math” and walk through some of that data to hopefully make it more accessible to teams. There are currently two posts: one is a basic introduction, the other looks at just how many points alliances scored in qualifying matches in 2012. We think the data might surprise you!
In the Beginning Rebound Fumble: Aim Low There is also a facebook page & twitter feed if you want to know when a new article is posted (should be about once a week). I'm pretty sure you can follow the tumblr blog itself as well... but I am not a tumblr expert. |
|
#2
|
|||
|
|||
|
Re: [EWCP] Presents TwentyFour -- An FRC Statistics Blog
I had a chance to read this last night and passed it onto 3929. Great info in here to use as an eye opener. Nice work Ian & all.
|
|
#3
|
|||||
|
|||||
|
Re: [EWCP] Presents TwentyFour -- An FRC Statistics Blog
I really enjoyed the post. There's a good mix of images & text describing the data and I was somewhat surprised by the extreme nature of some of the numbers. 4 points as a median in TeleOp for a given alliance? Ouch.
I think it shows how deceptively challenging the game was last year to a good number of teams and reinforces the importance of recognizing your team's capabilities and building your robot within your team's means. |
|
#4
|
|||||
|
|||||
|
Re: [EWCP] Presents TwentyFour -- An FRC Statistics Blog
Ian,
This is great stuff. One of the largest mistakes made by teams, year after year, veteran and rookie alike, is to overestimate scores. Even with the power of hindsight, they still fail to do it correctly. I have a lot of data points from previous games that are just as "surprising" as what you've presented for Rebound Rumble. I look forward to seeing your future posts! |
|
#5
|
||||
|
||||
|
Re: [EWCP] Presents TwentyFour -- An FRC Statistics Blog
The main thing that I take away from this is that Michigan district competitions, at least the ones that we attended, are way above average, score-wise. Especially Troy. Just looking at our own match lineup, the lowest score I see is 9. The average (just looking at matches we played in) losing alliance score is 31.4 points, and the average winning alliance score is 52 points. (I'm not even going into MSC- that's in an entirely different league.)
|
|
#6
|
||||
|
||||
|
Re: [EWCP] Presents TwentyFour -- An FRC Statistics Blog
First of all, thanks everyone for your kind words. We really hope teams can take this to heart and use it to ground their assumptions about 2013 and ultimately participate in more exciting matches.
Quote:
)Quote:
|
|
#7
|
|||
|
|||
|
Re: [EWCP] Presents TwentyFour -- An FRC Statistics Blog
Quote:
You may also notice that our data is being pulled from S3 at https://s3.amazonaws.com/twentyfour....12-twitter.csv Feel free to download that and use it in your own analysis. We're working on cleaning the 2010 and 2011 data still. If you see glaring problems with it let us know and if your provide data we can update the data set. |
|
#8
|
||||
|
||||
|
Re: [EWCP] Presents TwentyFour -- An FRC Statistics Blog
Great job and valuable data! Thanks for taking the time to do the analysis and to present the conclusions in such a clear and concise format.
Is it my imagination or do the game designers normally incorporate 3 scoring methods or strategies? And designing a robot to execute all 3 very well proves difficult because you run out of time (in the build season and during matches) or mass or both. We usually try to identify the game designer's intentions and optimize strategy and design around 2 strategies and/or scoring methods. Thanks Again! |
|
#9
|
||||
|
||||
|
Re: [EWCP] Presents TwentyFour -- An FRC Statistics Blog
Thanks for sharing your good work and astute observations. I agree that most teams overestimate the level of play and scoring, and that a team will do very well by setting a modest goal and actually achieving it.
If you were to break the scoring statistics down by week (or even by first half and second half of the competition season), I think you would find a significant increase in the scores. This is particularly true in Michigan and MAR where teams play in at least two events and have a real chance to improve. I disagree slightly with one of your conclusions, however. Although many teams over-reach technically and would do better with less, it is still good to reach a bit beyond your comfort zone. A functioning, "simple" machine is best at early events where it is playing against non-functioning "complex" machines that haven't reached their full potential. They will eventually reach a plateau and struggle to remain competitive. I think a team should understand their technical limitation and design within them, but you should always strive to be competitive against the "great" teams, not the pack. Some of us are fortunate enough to have an MSC to aspire to. As you imply, overestimating scores is a result of not predicting how the game will actually be played out. If your early brainstorming/strategy sessions don't result in a reasonably accurate version of reality, then it is hard to decide what functions you need to design into your robot. Week 1 of build season is the most important one by far. |
|
#10
|
||||
|
||||
|
Re: [EWCP] Presents TwentyFour -- An FRC Statistics Blog
Quote:
![]() In all fairness my team in 2006 won a regional by that formula of aiming low and actually working. Sure we shot from the ramp -- but we were one the few teams at the event who could reliable score our starting balls. Our target audience is really the teams that are missing out on eliminations (roughly that 50%), hence the name of the blog. Of course, we also hope it is somewhat useful to everyone. We don't want everyone to field a Dozer -- but we hope our analysis pushes some teams who haven't had much on the field success to emulate him. |
|
#11
|
|||
|
|||
|
Re: [EWCP] Presents TwentyFour -- An FRC Statistics Blog
Just a heads up guys, we've released another post talking about the exploits of Dozer (the little plow bot) over the years.
Dang it feels good to be a Dozer |
|
#12
|
|||||
|
|||||
|
Re: [EWCP] Presents TwentyFour -- An FRC Statistics Blog
Quote:
|
|
#13
|
||||
|
||||
|
Re: [EWCP] Presents TwentyFour -- An FRC Statistics Blog
That is correct. Co-op is an annoying game mechanic when you are trying to back out robot goodness from match data because it could do obnoxiously perverse things to team incentives. But we can at least give Dozer the 10 pts.
|
|
#14
|
||||
|
||||
|
Re: [EWCP] Presents TwentyFour -- An FRC Statistics Blog
Michigan regionals have a lot of good teams. We get Wildstang, Bombsquad, Winnovation, Team Hammond, Techno Kats, and a lot of other teams that score really well. Not only that, but teams around here actually help each other out a lot surprisingly. That plus since the scores get so high every year, a lot of teams fixate on getting their robot to do autonomous really well (you should see the autonomous scores, they are always high and really close) and doing really well in the end game just to get picked for elimination round. The top 8 teams at the regionals normally can do everything.
|
|
#15
|
||||
|
||||
|
Re: [EWCP] Presents TwentyFour -- An FRC Statistics Blog
Quote:
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|