View Single Post
  #24   Spotlight this post!  
Unread 19-02-2014, 18:24
Pault's Avatar
Pault Pault is offline
Registered User
FRC #0246 (Overclocked)
Team Role: College Student
 
Join Date: Jan 2013
Rookie Year: 2012
Location: Boston
Posts: 618
Pault has a reputation beyond reputePault has a reputation beyond reputePault has a reputation beyond reputePault has a reputation beyond reputePault has a reputation beyond reputePault has a reputation beyond reputePault has a reputation beyond reputePault has a reputation beyond reputePault has a reputation beyond reputePault has a reputation beyond reputePault has a reputation beyond repute
Re: Taking Robot out of Bag

I find the problem of new code very interesting. On one hand, you are most definitely gaining an advantage if you realize your code doesn't work. I don't care if you didn't do any diagnostics at all, or if you didn't try to fix it and redeploy, you now know that your code does this thing that you don't want it to do, and many times that alone is enough for you to figure out how to fix it.

On the other hand, many teams don't have version control. What if a team doesn't have the version of their code from when the robot was unbagged available? Are they just not allowed to deploy code to their robot? That would really hurt the demo.

I'm going to lean towards no: you can't deploy new code. Sure, it may mean that some teams can't take full advantage of this rule, but it is not much different than temporarily mounting components. FIRST gave us this wonderful oppurtunity, let's not push it.

That being said, Q&A is probably, once again, the proper route on this one.
Reply With Quote