| 2:20 is wild -- the street it's turning onto is clearly marked as a two-way in Google Maps [1] (which I understand provides the underlying data to Teslas). Why would the car think, no, it's best I turn onto the left side of this road? I'm also in awe of how fickle its predicted path is, especially when turning. Why commit to a new path for a tenth of a second and then change its mind again? This suggests to me it's placing way too high weight on poor quality telemetry. Heck, at 5:14 it can't even decide which street it wants to go down. Maybe it's just a UI thing (always displays the most likely path) and the underlying model is actually keeping both options open. At 6:45 it tries some insane passing maneuver -- I can't get over that one. Passing on the right, in a bus-only lane, planning to squeeze through the rapidly-closing gap of the car in front of it and a parked car, where there is currently a bicyclist. And it looks like the bicyclist is the only thing keeping it from doing that insane maneuver -- each time the bicyclist is occluded by the car in front (object permanence, hello?), it attempts to pass. I've lost count of the number of things this car doesn't understand, that it should to be on a road: * object permanence * reading basic text in simple print * logical connections between the map and road geometry * patience and commitment * understanding physics and geometry of other moving and non-moving vehicles * seeing stationary bright orange objects immediately in front of it [1] https://goo.gl/maps/EQfUnPrN52d9TVKPA |