The box visualization seems to be a waste CPU cycles.
OK, you are looking for objects by defining outlines, characteristics, and from multiple sensors.
Why wouldn't you just XOR the pixels on the display that triggered your response. This makes the object outline be exactly the opposite shade of the vehicle. So a black car on a black road gives it a white outline. A white car on a concrete road yields a black outline. A white road stripe on a concrete road becomes black outlined stripes around a white center.
What it skips is envelope sizing calculations, and a subroutine for selecting the color, size, and placement of the box and move and size it while still determining borders and features.
I guess it depends on how fast you want your code to run though. The trend today is write bloatware and skip the profiling. Assembler routines and calls? Meh, I gotz ghz, why do I need speed?
OK, you are looking for objects by defining outlines, characteristics, and from multiple sensors.
Why wouldn't you just XOR the pixels on the display that triggered your response. This makes the object outline be exactly the opposite shade of the vehicle. So a black car on a black road gives it a white outline. A white car on a concrete road yields a black outline. A white road stripe on a concrete road becomes black outlined stripes around a white center.
What it skips is envelope sizing calculations, and a subroutine for selecting the color, size, and placement of the box and move and size it while still determining borders and features.
I guess it depends on how fast you want your code to run though. The trend today is write bloatware and skip the profiling. Assembler routines and calls? Meh, I gotz ghz, why do I need speed?