FSDS bugs in recognizing signs, traffic lights, etc.

[3sr+buyer]

Found a few bugs in FSDS' recognition of traffic control devices.

A sign like this was seen as a green traffic light:

Another bug was seeing a speed limit sign on an off-ramp that had departed the freeway as being the speed limit for the freeway, shown in this Google Maps street view (US101 southbound near SFO airport):

Google Maps

Find local businesses, view maps and get driving directions in Google Maps.

www.google.com

 

[redmunds]

A sign like this was seen as a green traffic light:

That sounds correct to me. I wouldn't want it to be treated as a red light and stop. What would you expect it to do?

 

[JB47394]

A sign like this was seen as a green traffic light:

Don't worry about the visualization too much. Apart from the noodle, it's the V11 visualization. V12 doesn't use that information to decide what to do.

This bit is off topic, but AI DRIVR recently tested out the new non-USS Autopark, and it refused to back into a spot once because it believed that there was a pedestrian in the spot. The pedestrian was shown in the visualization and Autopark called it out. It was actually a trash bin, but the interesting bit is that the new Autopark seems to be tied into the V11 perception stuff. I guess when you want robotic precision, which Autopark delivers, you go with heuristics.