GRIP Thresholds

[Poseidon5817]

Why is it that GRIP thresholding operations (RGB, HSV, HSL) cannot accept numerical inputs to the Red, Hue, Saturation, etc. fields? Seeing as they are numbers, it could be convenient to set some of your image processing constants on the robot and transfer them to GRIP through NetworkTables.

[SamCarlberg]

You don't want to set vision constants in robot code to begin with. Every event venue has different lighting, which means you have to tune the constants for that event. So you'd either end up figuring out the constants in GRIP, sticking them in robot code, then send them back to GRIP... or just tune the sliders and hit save.

[Poseidon5817]

Originally Posted by SamCarlberg

You don't want to set vision constants in robot code to begin with. Every event venue has different lighting, which means you have to tune the constants for that event. So you'd either end up figuring out the constants in GRIP, sticking them in robot code, then send them back to GRIP... or just tune the sliders and hit save.

Yes that is the idea. But if we were able to feed numbers from Network Tables into thresholds, it would open up some doors in terms of auto-calibration that are not currently (easily) possible with GRIP.