5 ms·
The driving part is usually normal algorithm code and not machine learning though. Machine learning is for object detection, what the software does with that kn
by Jensson 5y ago
The driving part is usually normal algorithm code and not machine learning though. Machine learning is for object detection, what the software does with that knowledge is regular programming.
- dundarious 5y agoVery much so. The tens of thousands of hours of training is like the learning babies do while looking at jangling keys. Then the driving part is more static -- I'm not sure that it's entirely regular programming, there may be some training of models there. But my understanding is it's certainly not learning/training _while_ driving, and _almost_ certainly it's not even learning to drive. It's just doing more learning for object detection and tracking, like a baby watching the world from a pram. So I feel like no matter how many autonomous hours these cars accumulate on the road, they have effectively 0 hours of "learning to drive".
- Jensson 5y ago> I'm not sure that it's entirely regular programming, there may be some training of models there I doubt it, not anything serious at least. Machine learning isn't at the level where it can be used to navigate environments better than human coded algorithms can. Maybe if you had a datacenter worth of computing power to do it, like AlphaStar, but you don't have that in a car. And even if you had that I still doubt it, Alphastar had a perfect representation of the game and could simulate the effects of moves perfectly.
- dundarious 5y agoAgreed, I was trying to suggest that if it's not 100% static code, it's something like 1% models, 99% static code.
- thrashh 5y agoI think the only (but very major) difference is that is that animals and humans learn general knowledge. Someone with 100 hours of driving also has 16+ years of additional general learning. A driving AI has no general knowledge. It doesn’t actually understand what it is looking at. It’s not possible to make up reasonable responses consistently when you don’t know what you are looking at most of the time, machine or human. Have you ever tried to solve a technical problem before you read the documentation covering the basic concepts? You’re basically throwing shit at the wall until something sticks.
- njoubert 5y agoThat's not quite right. There are learned models inside the planning systems of most of the sophisticated self-driving car companies. Here's a public video that gives a few high-level examples: https://vimeo.com/618478174 https://vimeo.com/618478174 Full disclosure, I work for Aurora in the Planning group.
- Jensson 5y agoHow do you know those models are safe? I know Google said they didn't use machine learning for the driving part. Edit: To clarify, I wonder how you do this part: > make safe, predictable decisions on the road. ML models doesn't make predictable outputs. So you always need a system that can handle the ML model going haywire, since you have no way to prove that it wont.
- AlotOfReading 5y agoThis is probably a miscommunication issue. Waymo absolutely uses machine learning in the perception and prediction layers of the stack. Underneath that are a few layers of trajectory planning and controls code that don't necessarily need ML. As for stack accuracy and predictability, they're active areas of research for everyone, and part of the secret sauce. There's lots of little mitigations scattered throughout everyone's stacks for various particular issues, but no silver bullet.