The parent's checklist misses a bunch of things. For instance "1) Hookup a computer to the CAN-Bus network of the car". That alone is not trivial. It is trivial if you want to read the car's odometer, but good luck doing more than that. For instance, people are still trying to make sense of the reported battery cell voltages in the Nissan Leaf. All interesting features are not documented and require serious reverse-engineering. "Hooking up to the CAN-Bus" can easily become a task for a whole month, full-time. Not to mention that the most useful features for the self-driving part are probably not accessible by the CAN-Bus - people are still trying to unlock the doors of the aforementioned Nissan Leaf. Steering, acceleration and braking are unlikely to be on the CAN-Bus "2) Attach a bunch of peripherals" is also hand wavy, and same goes for the rest of the post.
It would be like dismissing SpaceX accomplishments by saying: "1) Build rocket frame. 2) build engine 3) Program flight software 4) Fill up the tanks with fuel 5) Push a big red button". The devil is in the details.
With that out of the way: if the events happened as described, this guy should be convicted of reckless "driving". Taking a prototype that had only started working a few hours prior to an actual test run in a freeway with other cars is insane. What about some simpler, more useful and less dangerous goal? Such as a lane-departure warning add-on for cars which lack that capability?
The article title is the worst part though. It's not "clever dude created a self-driving car prototype by himself". It is "Dude is taking on Tesla by himself". Which is bullshit.
EDIT: Fix typo.
We all take from the good work of those around us. But how many people seriously do things with that work? Not many, and disdaining people who do so is not productive or, in my view, a good thing.
We've also seen all the news from Google about their efforts and the pain points that they are experiencing. And this guy cobbles some stuff together and just puts it on the road. Most of us are not as smart as this guy, but that's just irresponsible. That just puts a bad taste in people's mouths.
It's not like it's unsupervised. Is it any more dangerous than taking a learner human diver out in a car?
Where's the sudden breakthrough? All of this is built on technology and work that came before it. The whole field. It probably only really started being worked on in earnest from a business context because big tech companies like Google had more money than they knew what to do with, and were willing to spend it on ventures with no likelihood of profit any time soon.
We have to draw the line somewhere.
I'm painfully aware of this. Ten years ago I ran one of the 2005 DARPA Grand Challenge teams. That's about what we produced with less than three full time equivalent people. We didn't have to handle other vehicles, but we did have to handle off-road conditions. Ours didn't make many mistakes, but it was very conservative and kept stopping to rescan its environment with a line-scanning LIDAR on a tilt head.
I'm scared of happy-case automatic driving implementations. Tesla went down that road and had to back up, removing some features. Cruise's PR indicates they were going that way, but they now realize that won't work.
> Not that outlandish for a talented person
What planet are you living on? I don't know what you did today, but I played with some jquery animations. This guy drove around in a self driving car that he built himself. It doesn't solve for edge cases? Neither do 90% of CRUD apps. Holy shit.
Give some credit where credit is due. This is not an ordinary or average outcome.
My point was that what 99% of HackerNews does is likely nowhere near as interesting or as difficult, so when the top comments are all shitting on someone who did something that's actually pretty amazing, HackerNews can go to hell. I mean that from the bottom of my heart. I'm done here.
Nevermind the ridiculous amount of engineering that was required to build all the tools he's using and the order of magnitude more engineering required to make this a safe, mass producible product.
But nah, let's just praise the founder, allow him to get rich while we all do the dirty work.
Claims of commercial viability or beating Tesla are a bit ridiculous, but this is pretty damn amazing.
> “I live by morals, I don’t live by laws,” Hotz declared in the story. “Laws are something made by assholes.”
> “ ‘If’ statements kill.”
> “I want power. Not power over people, but power over nature and the destiny of technology. I just want to know how it all works.”
2. Impress investors
3. Hire others to finish the job
4. Profit
Tesla customers invest in Musk. Musk invests in Hotz. Hots invests in developers. Developers in researchers. We're all delegating until we find someone who can finish the job. We're investing in people to hire the right people.
It doesn't work this way. You just move up the value chain.
Your comment screams a superiority complex, but I bet that you are actually a nice person in real-life. Hotz is doing good work, and everyone in the technical field is relying on work done decades before they were born.
You mean like this one, from Defcon in 2013?
http://hackaday.com/2013/07/26/defcon-presenters-preview-hac...
Or The Defcon 19 How To CanBus Hack Workshop, that taught classes about this in 2011?
http://www.canbushack.com/blog/index.php?title=learn-to-canb...
Unfortunately for him, defcon prefers original content, not someone claiming credit for what has been demonstrated repeatedly in previous years.
It's an impressive personal project, no doubt about that. It's however also important to recognize the difficulty of having a system that works in mass production and handles all kinds of situation. Like someone said earlier it's easy to have the car drive in clear day with very visible markers. The hard part is when it rains, when it's foggy, when things are less optimal, etc.
Once he get to that point he'll find that part to be a lot harder than what he's accomplished so far.
>> "If they had engineered a self-driving car, they would've engineered a self driving car".
You are just being absurdly accusative in your comment. That guy has done a self-driving car with nothing but tools available in the market.
Yeah, instead of going after the sensationalism, how about you discourage him from endangering the lives of others who weren't given the opportunity to make such a stupid decision?
This article is a hero worship piece about a guy rather than a story about the technology. It's like how you can't find an article about Theranos that isn't actually just a photo-shoot/celebrity worship article about its founder.
In the video, he claims to want to achieve level 3 driving. Let's see how he can do the following under non-perfect conditions:
- switching lanes
- stopping at lights
- turning cornerns
- turning left corners in traffic
Then we can move on to the more difficult situations.
Have all stop lights have a beacon that will tell cars their state, "the light is green on north south, red on east west"
Have exit signs have beacons as well.
Have you seen a traffic light? They're pretty substantial. How long would it take for you to make one in a hackerspace?
Contrast this with hacking OTA updates for traffic beacons. You might not even have to change any atoms around to do your dirty deed. You might not even have to be there physically.
The real issue here is that self-driving cars are probably the wrong place for that to happen in AI. At best, a solo project creates a crappy prototype where there was no product before (again, see Woz/Apple). The expectation for driverless cars is too high – they need to be 100% good, because your life is on the line, not 80% good.
What's the AI project that would blow people away, even if it was a shadow of a working prototype? I think that's the real question.
Even if AI cars are statistically better than humans on average, it's an issue of control. It's true that most accidents are avoidable and caused by human error, but most people are (perhaps overly) confident in their own ability to drive safely (this is also why people text and drive).
Robot that can build a better robot?
Finding a safe place to test an autonomous vehicle on a budget is hard, but not impossible. Our initial testing in 2004 was in a large unused Sun parking lot in Fremont.[1] (Sun got carried away with expansion plans, and started building a big facility there. They paved the parking lots and poured the building foundations, then stopped construction.) Later off-road testing was at the Woodside Horse Park. We also looked into testing at the Hollister off-road vehicle park, and discovered we could book a sizable area on a weekday for our exclusive use. We never used that, though. We'd also looked into using the old FMC tank test track in San Jose, but never found a good contact there.
In other words, I don't care if this guy is painted as a genius or script kiddie. He's not relevant in my life, and I will forget about him a week later. However, the lessons about machine learning and engineering that I can find in thsi article is the reasons I subscribe to HN (yes, I don't really know shit about these topics, and don't have enough time to fill gaps with real sources), and this comment is the most informative, just because he tries to cover what the article didn't.
This is just the start, not the end.
Human drivers might only see one of these cases a month, or 6 months, but not driving over someone in that case is what is critical. Not saying it's an impossible task, but IMO it will require a lot more training data than humanly possible for one person to generate.
Even pseudo-faking like we were trying to do, wherein as generated signal is injected into actual, recorded background noise, is fraught with problems. Anybody who tries to develop a control system based solely on such data is in for a rude awakening when they try it for real for the first time.
History keeps repeating
General cynicism isn't really adding much to the conversation in my opinion, since almost everyone here probably knows this already, and too much cynicism can put people off starting projects and people starting projects is something we should cherish.
I do think your point about emergency situations is substantive though. Perhaps he is only planning for self-driving while supervised by humans, but his idea for training as described (become an uber driver) would not at all produce the kind of dataset that would assure me that I would be safe. I think a lot of training with advanced drivers in simulators where you can have crazy life threatening situations would be the absolute minimum. I'd be worried that bad habits picked up on the thousands of uber rides would kick in during an emergency rather than the couple of situations that would be feasible to train on in real life.
What's better about an AI powered by neural nets is that you could train an AI to go offroading.
Get enough data and you've got a model for dealing with a given situation. Google's biggest strides with OCR, Voice recognition, Spam filters and other AI tech early on came from its ability to gather a huge corpus of data.
The real challenge is two fold. Gathering data, and feeding the AI with inputs with data actually matters. This is the secret sauce that Hotz refers to in the article as the information he's not willing to disclose. That information will become commoditized in due time (like low-latency optimization for HFT), but it will take plenty of institutional money & experience (Google, Apple, Tesla, Ford, etc) to get it there.
It's fairly easy to train, and verify a system for driving in well-behaved traffic. Unfortunately, the problem space of not-well-behaved traffic is far wider - and is very hard to gather enough data to train a system well.
What you're going to get is self-driving cars which handle 99% of driving just fine - and when they end up in emergencies, find the human 'driver' to have dozed off at the wheel. (All-in-all, their safety record might end up better then the status quo - but that's not a certainty.)
The reactions of NN to unusual stimuli are likely to be counter-intuitive at best and unpredictable at worst.
Machines, on the other hand, are a different story.
It seems that the technology has already, or is very close to approaching human levels of proficiency on the road. If specific use cases (offroad, snowpacked road etc.) are problematic, they can be limited or prohibited in the mean time.
I have no inside knowledge, but I would be very surprised if Google's self-driving cars use neural nets as a significant component right now (which isn't to say there aren't people exploring its use).
I could probably do this using ROS, opencv, and pcl. At least on a level where the car could recognize the road well enough to drive on it, but I imagine both my car and his car are nothing that any sane human would want to sit in. That last 20% focusing on safety and edge cases is going to be 100x the work/innovation/testing/staff/code/talent/smarts here.
As a side note, I am intrigued by the idea of a FOSS self-driving car. Its a little worrysome we'll never see the code Tesla, Mercedes, etc are using.
So yes, it's an amazing project for a single person, but it's not really a self-driving car.
Could you explain on what basis you claim this? Do you have intimate knowledge of his prototype, the amount of work he put in, or the novel ideas that he brought to the project in addition to integrating pre-existing tech?
From what I can understand, your argument seems to be "lets see if I can guess what he did". If you're an authority in this field, then your guess could be very accurate I suppose.
OK, maybe it's BS, but he's not saying what you say he's saying.
I would be very surprised if you got deep reinforcement learning to perform well on a self-driving task, even on a highway. If you did, well, your faculty position at Stanford is waiting for you.
more states? add neurons! more search space? add layers!
except they have unpredictable resonances, especially multi-layer networks:
http://www.i-programmer.info/news/105-artificial-intelligenc...
they're just starting to understand this, but I believe the myth of the 'do it all dnn' is gonna die. it's time to start thinking about cluster of independent neural network, supervising each an independent aspect of the search space and/or each other.
Small personal example: my family lives out in the suburbs. My dad works in a neighboring city. His commute is about a half hour, 20 minutes of which is a straight shot on a major highway. I'm sure he'd be willing to pay a few hundred to reclaim that 20 minutes each way to read a book/the newspaper, check his email, browse the internet, etc.
It'd also be good for road trips.
Groves "Principles of GNSS, Inertial, and Multisensor Navigation Systems" contains a good description of the various technologies used and their accuracy limits for navigation.
Consumer grade MEMS are fine for airbags, the pedometer in your phone, but are not sufficient for intertial navigation, even when aided with other sources. At around the $2K-30K you get systems that can provide accurate navigation for up to 2 minutes or so. They are used in things like missiles.
Aviation grade IMUs need to meet SNU 84 standard, which requires a maximum horizontal position drift of 1.5km in the first hour of operation. These will run 100K and up. Marine grade (subs, rockets, ICBMs) run $1 million and up, and have a maximum drift of 1.8km per day.
None of them are good enough for autonomous cars w/o sensor fusion.
I am totally for a computer telling me when I'm driving dangerously because I'm distracted or tired.
Take the case of the Wright Brothers who faced two well funded adversaries. Samuel Pierpont Langley had a chair at Harvard, worked at the Smithsonian and had among others funding him $50K from the US War Department. Alexander Graham Bell, the inventor of the telephone, was an avid aviation enthusiast and an already wealthy man. One of Bell's assistants was Glenn Curtiss who went on to found his own plane company.
Who would bet on two bicycle mechanics from Dayton, Ohio? No one, yet they were the first to fly.
The first popular microcomputer would surely come from IBM or HP yet it didn't. Two guys in a Cupertino garage built it and neither of them was a college graduate.
This guy may fail but I am not going to bet against him. In fact I hope they televise the race between the Comma and the Tesla. I'll bring the popcorn.
I.e. they did much more than simply throw some ideas and parts together and see what stuck, like every other contemporary experimenter.
Ever since I played around with Prolog in the nineties I came to believe, just like digital eventually triumphed over analog, that neural networks will eventually triumph over rule sets based software. I did not know when it will become apparent, but I firmly believe that it is coming.
Learning for the AI does not have to be from real world experiences only. Simulated/controlled emergency situations would help as well! Further even if the 2K lines of code stretches a bit more to deal with unknown situations that isn't so bad either
Here has been dedicated on making maps at a quality level that is needed for automous cars. A few issues with the data that is available currently is that the data isn't very detailed, and you're at the mercy of volunteers (tiger(old), openmaps data), or for a company that's main focus isn't maps. (Google)
What if you could simulate these conditions in a safe/controlled environment, and remove the driver from harm via remote control? Maybe build a virtual world that simulates the inputs as best as possible. That would be the cheap way, although you may lose fidelity.
If you had enough money you could build a simulated town/city, similar to a movie set, that throws all possible dangerous scenarios at you and operate the car remotely through these scenarios.
http://velodynelidar.com/lidar/hdlpressroom/pdf/Articles/The...
I think it's likely that much more of self-driving car development is smoke and mirrors than people realize. Best case scenarios are promoted as examples of how innovative a company is. Great PR, not necessarily a practical result.
This is a sensor limitation. They have fully admitted this several times (heavy rain too). Equating the fact that this guy can't handle any emergency situations with a sensor limitation all of the lidar systems suffer from is stupid.
Google has shown many times that they have logic to handle routes around obstructions, construction, etc as well as cars running red lights, pedestrians walking into the street, etc. At least read up on something before you call it smoke and mirrors.
http://www.slate.com/articles/technology/technology/2014/10/...
I'm not saying it won't ever happen, I'm not saying there haven't been developments in the technology. But people seem to have a disconnect in expectations of where the technology is, and where marketing departments for these tech companies want you to believe the technology is.
If SSD = Solid state disk, then HDD = Hard disk disk.
HDD = HARD DISK drive
SSD = SOLID STATE drive
What he did is impressive. But the results are not that outlandish for a talented person.
1) Hook up a computer to the CAN-Bus network of the car [1] and attach a bunch of sensor peripherals.
2) Drive around for some time and record everything to disk.
3) Implement some of the recent ideas from deep reinforcement learing [2,3]. For training, feed the system with the oberservations from test drives and reward actions that mimick the reactions of actual drivers.
In 2k lines of code he probably does not have a car model that can be used for path planning [4] (with tire slippage, etc.). So his system will make errors in emergency situations. Especially since the neural net has never experienced most emergencies and could not learn the appropriate reactions.
And guess what, emergency situations are the hard part. Driving on a freeway with visible lane markings is easy. German research projects autonomously drove on the Autobahn since the 80s [5]. Neural networks were used for the task since about the same time [6].
[1] http://www.instructables.com/id/Hack-your-vehicle-CAN-BUS-wi...
[2] http://arxiv.org/abs/1509.02971
[3] http://arxiv.org/abs/1504.00702
[4] http://www.rem2030.de/rem2030-wAssets/docs/downloads/07_Konf...
[5] https://en.wikipedia.org/wiki/Eureka_Prometheus_Project
[6] http://repository.cmu.edu/cgi/viewcontent.cgi?article=2874&c...