Quote:
Originally Posted by Ninjastahr
But seriously, if your team has had trouble in the past with making practice matches or inspection, don't change your robot at competition! Last year, my team added a can grabber between Quals and Elims (or playoffs, or whatever they were last year) and it was definitely not worth the time and effort it took to do in time. If you're not 100% sure you can add it before practice matches, don't do it.
|
I can definitely understand minor tweaks and fixes, but I would agree that making big changes at competition is stressful for all involved. If you have to do it because your robot just isn't functioning the way it needs to, that's one thing. If your robot is working and now you're being tempted to add that one more little feature, resist the urge. This is where things start to get crazy.
We didn't have our auto modes working properly when we started quals at GTRC. Students worked on it every spare minute they could outside of our matches. There were many opportunities that we could have deployed the very latest and hoped for the best. But we all decided, as a group, that since the drive team was doing well with what they had, we were not going to risk screwing up, crashing the software, or other "oops" mistakes by deploying code without first fully testing it on the practice field. Did we lose some potential auto points because of this? Yes, definitely. But the software students, the drive team students, and the mentors were all much more relaxed and less stressed, knowing that "it'll be ready when it's ready".