|
Re: Lessons Learned - The Positive
- Twitter was one of the best decisions this year. It not only kept non-attenders updated on what was going on, but it also sets the stage for more live coverage of the events in the future.
- I'm pretty sure the GDC learned alot (not necessarily lessons) about cumbersome rules. Regardless of whether or not teams agree with a set of subsystem rules, the GDC knows how to make rules that are meant to work together more clear. I'm pretty sure they also realized that using bitmaps in the official rulebook may not be the best way to do demonstrate things since they can become a source of great confusion.
- The new control system is fantastic. The camera was easy to use. The DS data interface was great once we re-wrapped the data our own way, and the new driver's station allows for a myriad of controls in future years compared to previous. I'll also note that our team never had issues with static, etc, and meticulously read every control system tip, trick, and update. While our team probably will not switch to Labview for several years, we found ways to push the limits of some areas of the cRIO and look forward to what new features will allow us to do in the future.
- The FTC game was simple enough that teams perfected their robots by the time the championships hit. Our own FTC team was averaging 120 points per game (double what we did at regionals) yet we were still being beat by 5-10 points in our matches. This is great (no sarcasm, promise!)!. The FTC matches were exciting to watch, and I know our FTC kids had a blast in building the bot because they were beating down the school's doors to come in every day to work on the bot. Ok, so the excessive pricing scheme needs to be addressed, perhaps by introducing an alternate supplier that will induce competitive pricing. But other than that, I'm mostly happy with the current FTC setup.
__________________
Drive Coach, 1885 (2007-present)
CAD Library Updated 5/1/16 - 2016 Curie/Carver Industrial Design Winner
GitHub
|