opencv a place to start

[cpapplefamily]

If I'm reading your suggestion i should test the opencv programming on my Ubuntu partitioned laptop This way i can stay in the java language. I have seen loads of code to procces through i just want to be sure as I'm teaching my self how to use it that I'm not ....hate to say waist..... a bunch of time in a language i will not be using. My trouble is i don't spend enough time in one language to GREAT. Arduino C, Raspberrypi Python, now FRC Java. Do teams often offload the vision to other processors like pi's? Will the gearsbot simulator run vision?

Thank for the start.

[TheHolyHades1]

Originally Posted by cpapplefamily

If I'm reading your suggestion i should test the opencv programming on my Ubuntu partitioned laptop This way i can stay in the java language. I have seen loads of code to procces through i just want to be sure as I'm teaching my self how to use it that I'm not ....hate to say waist..... a bunch of time in a language i will not be using. My trouble is i don't spend enough time in one language to GREAT. Arduino C, Raspberrypi Python, now FRC Java. Do teams often offload the vision to other processors like pi's? Will the gearsbot simulator run vision?

Thank for the start.

Hey,

It really depends on what your team is using, and what you're feeling comfortable with. I know it's *possible* to run vision code on the roborio, but as the system is new, you'll likely be able to find greater support if you offload the computation to a coprocessor, like a raspi as you mentioned.

The raspi is a linux system, so writing your code on an Ubuntu partition is recommended for similarity of the systems. That, and it's *significantly* easier to get all of the dependencies installed in the Ubuntu system vs the windows one. As for language, there exist openCV ports for a variety of languages. The "primary" one is the C++ version, but there exist C and Python versions at the very least, and I'm sure ports exist for Java and others. The nice thing about these ports is that the functions are essentially the same among the languages - the Python and C++ version, for example, have the same function names with slightly differing parameters (by type). So, learning opencv in a particular language should let you port your code to another language quite quickly, and your effort won't really be wasted by any means.

So, my recommendation would be to pick the language that your team uses for their overall code (that is, pick between Java and C++). If you choose the other, you still can't really go wrong.

EDIT: Just read that your team runs Java. So choose Java.

[chsahit]

If you are using the RPi I would suggest staying away from Java/Python, the overhead would make vision processing a pain. Try C++. A few years ago, MORT stripped down a laptop and put it on the robot, it's surprisingly straight forward and not as heavy as one might think. I believe there is a way to use network tables and actually do all your processing on the driver station itself. Just send the data from the robot to a client program on your DS, analyze it there, and send it back.
Feel free to message me about questions or if you want to see code!

[F22Rapture]

Originally Posted by chsahit

If you are using the RPi I would suggest staying away from Java/Python, the overhead would make vision processing a pain. Try C++. A few years ago, MORT stripped down a laptop and put it on the robot, it's surprisingly straight forward and not as heavy as one might think. I believe there is a way to use network tables and actually do all your processing on the driver station itself. Just send the data from the robot to a client program on your DS, analyze it there, and send it back.
Feel free to message me about questions or if you want to see code!

Not really true. I'm not sure about the Java bindings for OpenCV, but the Python bindings only have an overhead of something like 15%. All of the work is still being done in the same native code.