Quote:
|
Originally Posted by Chris Hibner
One possible comprimise is to give teams the control systems and sensors one or two months in advance. If we had that extra time to work with the camera, I'm sure we would be capping vision tetras in autonomous. We decided that the time wouldn't allow it so we wen't with a more tried and true autonomous method.
|
That's a really good point. I'm not sure it would have made the difference for our team, but I'm sure it would have helped out a lot of other teams if they had had the camera ahead of time and had already "trained" it to follow objects. Plus, you'd know up front (at the beginning of the build season) what it's capabilities were and therefore have a better idea of whether or not it's worth pursuing. I don't think it'll solve the problem but it would be a big step in the right direction.
Quote:
|
Originally Posted by Tom Bottiglieri
http://www.chiefdelphi.com/forums/s...2&highlight=FPG
This wont give programmers anymore time with the bot, but if they dont have to debug all the systems or worry about fixing problems in their custom code, they can spend more time tweaking the real bot for competetion.
|
That's a decent idea, but I just don't think it'll solve the problem. No matter how well the code is written or how early, when it comes down to it you always need time on the actual hardware (i.e. competition robot) to test it, and I think that is the limiting factor for most teams. As it stands, the mechanical groups will take up nearly every minute of build time getting the robot designed and built (and they need it, too!). Unless there is
some way to guarantee the software people time to test and debug their code on the competition robot I just don't see autonomous improving much from what we've seen in the last few years.