Quote:
Originally Posted by EricDrost
I think the value of a vision system greatly depends upon the game.
|
Right; this year, while some really good teams used targeting, I'd argue most consistently good teams used the pyramid or their drivers for alignment.
I'd also like to point out that humans are almost always more intelligent than an algorithm.
Quote:
Originally Posted by Jared341
But I would strongly recommend that unless software is a particular strength of your team, keep it "out of the critical path" and have a fallback plan in case it just isn't ready on time.
|
Our team's strategy in 2012 initially required lots of vision targeting and feedback/closed-loop systems. We felt confident we had the mentor-student experience, and had good results on our practice field. However, come regional, we had lots of problems (both with software and with actual part failures), and ended up learning some hard lessons.
<Moral>
As with any subsystem, part, or component of the robot (mechanical, software, or otherwise), don't let it's ability to function decide whether or not you are able to execute your strategy. Always build in redundancy, overrides, and in case of cascade failure, the ability to quickly replace.
</Moral>
I don't know that moral that affects your particular system exactly, but there's my $0.02.