I haven't even tested the code yet but i know that the sample seems to filter out all but red while we need it to filter out all but green

Would it be better to replace the hsv threshold with rgb

Re: Values for Image Proccessing
 

It is a bit difficult to talk about these with no images.

The Threshold operation compares pixel values and returns a Boolean masked image. The image only has two values, 0 and nonzero. Vision Assistant and other tools will typically display this with two colors. The colors have no relation to any original colors.

If the threshold is masking out the wrong color, change the hue. I attached an approximate hue wheel from a LV panel. I highly recommend you open up Vision Assistant and experiment with an image and the color threshold block.
The block supports RGB, and various HS(IVL) versions.

There was a question about switching to RGB, and that will be a bit faster to process, but I think you'll find it far less accurate for specifying ranges. But the cool thing about Vision Assistant is that you can experiment, discover things, and ask questions.

Greg McKaskle

Thank you for all your help

Re: Values for Image Proccessing
 

Last year for image processing we put the camera with the LEDs on the robot, lined it up, and used the driver station image. If you look at the bottom of the image you should see RGB values. Put the cursor on the highlighted target and record tose values, then plug them into your code. Now, if you are doing this in your work area, these values are going to be different when you take your robot to competitions. It will need to be calibrated each time you move to a place with different lighting. I hope this helps! Good luck with Java! :)

Re: Values for Image Proccessing
 

Do you recall what the values were? Do you have your camera set to automatically adjust white balance and exposure?

If you were to set the camera up to where the majority of light you care about comes from the LEDs and the camera isn't adjusting settings, I suspect the values won't need to be calibrated or the calibration will not change by much.

Greg McKaskle

Re: Values for Image Proccessing
 

This was our thresholding code, and the lighting truly did effect the values. we found this out when our auto targeting would work perfectly at our build facility, and then not work at competitions. we found that at the competitions, the thresholds were drastically different.

Re: Values for Image Proccessing
 

I was asking about build versus competition values. Is that the commented code change?

Also, do you know if the exposure and white balance were set to auto or not?

The commented code change is actually not that big a change. It is basically saying that the green lower limit needed to change by 20%.

Do you have any images used to do the calibration?

Greg McKaskle

Re: Values for Image Proccessing
 

Yes i think it is what the commented code is, what I meant by the values drastically changing was that the results changed. the robot went from snapping directly to the target with a push of a button to jumping around and not staying still because it couldn't see the target properly. I don't remember changing anything else, so the exposure and white balance must have been set to default. we used a false color image for the robot to parse, filtering everything but the colors within the threshold.

Re: Values for Image Proccessing
 

The default settings of the camera are automatic exposure and automatic white balance. These will give more variability than if you calibrate and keep the settings constant. I'd love to be able to set them from code or configuration, but the camera doesn't have full support for that. I think that you may want to experiment with calibration, as discussed in the white paper and then test the results in the shop, outside, perhaps with some work lights or bright flashlights shining on the targets or the robot. No vision system is immune to lighting changes, not even your eyes, but knowing what will break it and what won't is pretty good stuff.

Greg McKaskle

Re: Values for Image Proccessing
 

What I did last year was just look at the apparent size of a vertical side of the target, and then compare that to the actual size. It's simple to figure out range from that proportion.

I did have to correct the reported values, but I'd recommend just getting the first part of what I said outputting values, then do some empirical testing, plot the values in excel (computed distance v actual) and then generating a trend line. The equation of that line should correct your calculated distances pretty well.