Tesla Is Building Its Own AI Chips For Self-Driving Cars (techcrunch.com)
Yesterday, during his quarterly earnings call, Tesla CEO Elon Musk revealed a new piece of hardware that the company is working on to perform all the calculations required to advance the self-driving capabilities of its vehicles. The specialized chip, known as "Hardware 3," will be "swapped into the Model S, X, and 3," reports TechCrunch. From the report: Tesla has thus far relied on Nvidia's Drive platform. So why switch now? By building things in-house, Tesla say it's able to focus on its own needs for the sake of efficiency. "We had the benefit [...] of knowing what our neural networks look like, and what they'll look like in the future," said Pete Bannon, director of the Hardware 3 project. Bannon also noted that the hardware upgrade should start rolling out next year. "The key," adds Elon "is to be able to run the neural network at a fundamental, bare metal level. You have to do these calculations in the circuit itself, not in some sort of emulation mode, which is how a GPU or CPU would operate. You want to do a massive amount of [calculations] with the memory right there." The final outcome, according to Elon, is pretty dramatic: He says that whereas Tesla's computer vision software running on Nvidia's hardware was handling about 200 frames per second, its specialized chip is able to crunch out 2,000 frames per second "with full redundancy and failover." Plus, as AI analyst James Wang points out, it gives Tesla more control over its own future.
From the previous thread about Tesla, I expected this headline to read "Tesla is now building their own arcade cabinets".
#DeleteFacebook
You know if you've ever said anything nasty about Elon.
Now, his vehicles know.
Be afraid. Be very, very afraid.
Mimetics Inc. Twitter
For better and worse, keeping things proprietary means it's by definition both closed source, and tested only to one's own environment. Although it produces fast yields, it doesn't have many eyes. Many eyes and many hours are needed to vet the integrity and edge cases (like cliff edges) before safety can be assured.
It's a risky, expensive, and proprietary endeavor. If everyone (systems builders) were using similar development, the testing age could be completed in a concurrent time, rather than a serial/iterative time. I'm betting against this turning out well.
---- Teach Peace. It's Cheaper Than War.
I'll be in the basement hiding from the cars
-- Thou hast strayed far from the path of the Avatar.
"We had the benefit [...] of knowing what our neural networks look like, and what they'll look like in the future,"
Really? If they take their neural network development seriously I don't think they know what their networks will look like in ten years. It's a research area in the middle of a transformation. Using architectures molded into hardware is probably just costly and will act as an antagonist to innovation. I don't think having 2000 vs 200 frames per second right now outweighs that downside.
A car travelling at 90 mph is moving about 4 cm/millisecond. So going from 200 fps to 2000 fps is going from 20 cm to 2 cm per cycle. What's the use of recognizing a car every two centimeters? For a jogger at 9 mph it's down from 2 cm to 2 mm. It's neat and all but I don't see how that necessary to react in the time frames a car needs to react. Even if it takes 3-4 frames for the car to get a motion vector 0.2 seconds is still way quicker than a human and 0.02 seconds doesn't bring that much.
Live today, because you never know what tomorrow brings