|
Re: cease all software development?
If I were an outsider reading this rule, I would say the rule means just what it says. Put the pencils and laptops down and don't think about coding the robot until you see it again at the next event. Then code and test away...
However, as a participant, to me anyway, the worst thing about the "no software development" rule is that if a team doesn't have a good code going into ship day, it's going to be REALLY hard to get autonomous mode dialed in. How are teams going to be able to dial in their autonomous mode that tries to fire into the center goal at a regional? During their 2 or 3 practice rounds where they might get one or two shots at it? And then during the rounds when it counts? It's not like you can do it in the pits or there will be balls flying everywhere.
IMHO, this rule makes me sad and I think it leads to many autonomous modes where six robots sit there for 10 seconds at the beginning of a match...especially at the earlier tournaments.
I also understand what I believe the rule is trying to do...make it fair for the smaller, less funded teams who can't afford a second robot or RC. However, I think a lot of these teams are usually the ones who get things done during the last few days and have the least amount of time to program. So why not let the teams keep the controller boards to make it fair to everyone?
Of all the rules this year, this is the only one that I think is detrimental to the quality of the competitions... No offense...just my opinion...
__________________
Donald F. Wright Jr.
Product Manager
AVL Instrumentation & Test Systems, Inc.
|