Quote:
Originally Posted by joecloud
We would not have been able to get the code to work if another team had not let us take a look at their code. Which was based on the use of the ds for processing. Once we did get it working and calibrated to the competition field we tested it on the practice field and it worked perfectly every time. Once we got to the actual competition field though our bot swerved left or right randomly. (jaguar was setup incorrectly) so tape was often left out of view of camera.
|
That is the exact scenario here. I would like to accredit Team 1706 for answering every question I had. That really saved me hours from reading the
RefMan.
The thing that really helped me is that they shared all their previous years worth of code with me, so I as able to understand how HSV works, how findContours works, and even how the OpenNI-OpenKinect-OpenCV implementation works. I guess I should have taken some of the advice from some of the CDers, who were telling me that the learning curve is quite large.
Thankfully, that doesn't scare me. I literally used OpenCV in labs, where the teacher didn't have access to expensive equipment. Basic color tracking did the job though.
Some advanced programming knowledge, like OpenCV can be very handy in your toolbox because you never know when it will be useful, even for adding features to your favorite video editor!
My latest stable code that works runs in the DS. However, I switched to OpenCV Linux so I can run embedded without shelling hundreds of dollars for an x64 system.
Next year, I want to learn even more hardware-level programming and develop my own communication protocol to rapidly transfer a lot of data between multiple wired computers.