Quote:
Originally Posted by IronicDeadBird
Interesting thought, perhaps next year all design should be done based off a list of possible ideas and a magic 8 ball...
|
Hey, in your original question you didn't specify "on actual field"
If it's any consolation if it doesn't work on a real field I'm gonna have a REALLY long day tomorrow trying to debug it from 2500 miles away.
That being said, I've found the iteration cycles of GRIP to be unparalleled. The ability for students (and me) to ask "what if" is incredible. It's missing some features I'd like to see (better ability to do feature refinement most notably).
For reference, we had two different groups of students working in parallel. One was using GRIP and the other was building a custom solution running on a beagle bone black using python and opencv. The core issue we had with the BBB solution was communicating to the RoboRio. GRIP handling that out of the box has been the real difference maker in that it allows the robot code to treat the camera as essentially a simple sensor we can access from Smart Dashboard.
In short, I hope it works on the field because I'm a big fan of it. But at the same time, I hope it doesn't because it means I'm gonna have to work that much harder to find a competitive edge in the future
(But no, I really hope it works)