Quick Question about Threads

[JesseK]

Originally Posted by joelg236

If it take 2-5 seconds to process one image well, versus doing 10 images in the same amount of time badly, it seems like an obvious decision to do it once thoroughly.

I can honestly say that properly processing an image well doesn't take even 2 seconds. However, if it did, the good engineer would find the balance of quality vs time. Strategy of a given game may not allow a 2-second waiting sequence if the goal is to have a top-notch performing robot with respect to using vision tracking as part of scoring (auto-aim in '12, 2-tube auton in '11, 5-ball auton in '10, etc).

[apples000]

For rebound rumble, we used LabVIEW to program our robot. We actually found that it was much easier to process about 8-10 images per second and just use a PID loop. The tracking wasn't perfect, but it was simpler to implement than doing the math to figure out the change in angle that our turret needed to have. Also, it was easier to build because our turret never had position feedback and used the image coordinates instead. We were able to sucessfully drive back, tip the bridge, then drive forward and make both baskets lining up using this method, and my goal was to do something similar in Java, which we will use this year.

[joelg236]

Originally Posted by JesseK

I can honestly say that properly processing an image well doesn't take even 2 seconds. However, if it did, the good engineer would find the balance of quality vs time. Strategy of a given game may not allow a 2-second waiting sequence if the goal is to have a top-notch performing robot with respect to using vision tracking as part of scoring (auto-aim in '12, 2-tube auton in '11, 5-ball auton in '10, etc).

Sorry if that sounded like I was using 2 seconds as some sort of specific number. Like I mentioned, I have no good experience with vision processing and I just used 2 for the sake of the point.