Thread: What margin of error is tolerable in FRC?
View Single Post
  #9   Spotlight this post!  
Unread 04-01-2012, 17:50
davidthefat davidthefat is offline
Alumni
AKA: David Yoon
FRC #0589 (Falkons)
Team Role: Alumni
  
Join Date: Jan 2011
Rookie Year: 2010
Location: California
Posts: 792
davidthefat has much to be proud ofdavidthefat has much to be proud ofdavidthefat has much to be proud ofdavidthefat has much to be proud ofdavidthefat has much to be proud ofdavidthefat has much to be proud ofdavidthefat has much to be proud ofdavidthefat has much to be proud ofdavidthefat has much to be proud of
Re: What margin of error is tolerable in FRC?
Quote:
Originally Posted by Andrew Schreiber View Post
Check the rules on this one.

So here's the deal, good software can make a good robot great. Bad software can make a good robot bad. Good software can't make a mechanically incomplete robot good. What I'm trying to say is that, for FIRST, you don't always need fancy controls, you don't need 100% accurate movement. You need a 100% reliable drive train. A trained drive team. A solid scouting/strategy team. And a dedicated team of students and mentors.
I thought that if the code was publicly available before the kickoff, it is all good. It is on a public repository on GitHub as I type.

As far as your other comments go, I personally agree. However, I have to do everything in my power to make this year's robot best as I can. We are clearly lacking in the hardware aspect of the team and I am considering even doing the electronics this year because the main electrical guy graduated last year. It is my last year and I can't just sit around and expect someone else to do anything. That is partially the reason why I started writing the code two weeks ago and testing months ago. I'm just trying to do the best I can.
__________________
Do not say what can or cannot be done, but, instead, say what must be done for the task at hand must be accomplished.
Last edited by davidthefat : 04-01-2012 at 18:08.