|
Is vision processing on the crio plausible?
It's definitely possible, but is it plausible? I heard it takes up a lot of memory, and slows down the code. From my understanding the best way is such: (onboard comp/comp. dashboard)>(classmate w/ dashboard)>(crio).
What if you can turn vision tracking off and on when needed? Imagine this: a robot is lining up to shoot by the pyramid, standing still running no motors except lets say the shooter and a lifter/hopper. I push a button to do tracking, and tracking starts on crio, finds target, and shoots all the discs. Then tracking stops right after. With such an occurrence, will the tracking slow anything else down? It's not running the whole match.
And If it has a big impact on processing power/speed, how "lean" should the code on the crio need to be successful?...how lean?..how lean do you like your meat? just kidding..
|