View Single Post
  #2   Spotlight this post!  
Unread 02-06-2010, 08:19 PM
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
 
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,748
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: Camera ROI Usage?

I'm curious how many timing samples were used to determine the effect of the ROI. Unlike most sensors, jpeg cameras aren't very realtime friendly. First off, the jpeg returned from the camera is a different size and will take a somewhat different time to decode. Secondly, the algorithm for finding contours takes many shortcuts if it can, so the timing is very dependent on what is in the image. This means that a slim 2ms difference is probably well within the noise of the timings.

To answer your question about the ROI, I would expect it to speed up the processing by some amount, but will have no affect on the jpeg decoding which is also a pretty big cost.

There is a white paper on the NI site about the vision code, and the primary thing to speed up the processing is the threshold. The paper doesn't go into using the ROI primarily because it is difficult to use unless you have an idea of where the robot is on the field and how big the target should be.

Greg McKaskle
Reply With Quote