View Single Post
  #11   Spotlight this post!  
Unread 16-01-2014, 06:41
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,751
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: Vision Tracking the Hot Goal LEDs

What you really care about is what color the camera sees when it captures the LEDs, not what color the LEDs produce.

If you had a perfectly calibrated camera, knowing the LED wavelength would be all you'd need. But we don't have perfect cameras or perfect eyes.

One of the first things the cameras do is to combine the component light values into a colored image assuming a specified white balance. This is there to adjust for different ambient lighting such as outdoor sunlight versus indoor fluorescent. But this shifts all colors in the image. It doesn't know what pixels represent an LED producing light source and the pixels that are reflecting ambient light. The camera offers different white balance settings including an auto setting that analyzes the image and calculates the most likely type of ambient lighting. But all of these shift the colors, breaking simple math comparison approaches.

I think the first challenge is to determine if you can even get the camera to see the colors. Bright light sources saturate the sensor, resulting in a white spot, not a colored spot. Perhaps you can simply use the monochrome spots as a template for image recognition?

Greg McKaskle
Reply With Quote