Why We Should Adopt Driverless Cars That Kill People
medium.com
medium.com
This article is clearly written by someone who has never worked on a safety critical system. There is a method for establishing risk and making risk-benefit tradeoffs, not just feeling certain. If we did that many more people would be killed.
If the author is arguing about public scrutiny, then I generally agree with the argument, but existing safety engineering practices will work for driverless cars.
Source: I work on hardware and software for surgical devices (among other things).
Just create a big old test suite, procedurally generated. It would make for a nice game and driver training tool too. Verify against average and expert drivers to set grading. Additionally get statistics about prevalence of bad driving, which will allow you to check if the driverless system is safe enough using plain old cost-benefit. Moreover, include assisted driving systems (emergency takeover) in the evaluation.
No need to require perfection, failing gracefully is also acceptable. For example, in a weird situation, the car could slow down and engage notifications at drivers.
An example of this is babies in laps on airplane. What is the benefit? People with kids will fly rather than drive. But are kids safe on a parents lap? No not really? Are they SAFER on a parents lap in an airplane than in a cross country trip in a car-seat? It turns out they are. So you have babies in laps on airplanes. It's an analysis of safety not a mitigation of situations where people might, with extremely low probability, die.
That's not as simple as the writer seems to think it is. Autonomous vehicles can only interface with the world via sensors, and sensor data that looks real, but is actually computationally generated, is one of the best ways to make a model overfit. It can learn the exact function and simplifications a developer has made in order to generate the fake data.
Then you can say "alright, record the data and modify it". But you can't actually modify, for instance, point-cloud data that much to account for arbitrary viewpoints. What you can do, and what most companies do afaik, is record the data as a "unit test". The car then responds to the test and, given the result actuation, it is evaluated whether the test passed (e.g.: you want to drive into the sidewalk? test failed). So if the car wants to do a correct maneuver in the test (i.e., one that passes the evaluation), but it is different than the maneuver the test has recorded, then you suddenly don't have the data to assess how well the car did. I know there are ways companies use to solve this but I assume it's not generating data, given the problem presented above.
tldr: generated data isnt as straight forward and can lead to bigger problems later on.
Wouldn't engineers notice that when examining why the car failed the test, and modify the test to allow the new correct maneuver?
Instead of generated data, try hallucinated data using AI to generate weird situations. Albeit random training is also pretty good, as is parameterization.
You can stop reading there. Unfortunately we are not living in an Open Source world. Walled gardens will keep improvements for themselves, knowledge will die with dying companies, version incompatibilities will create a complex situation.
I am very willing to believe in the thesis of the article, but the way the Software industry has been evolving recently does not give me much hope.
The author is not shy about making other assumptions, either: "Sebastian Thrun postulates that, when subject to real-world conditions, AI can double its performance every 18 months" "let’s assume that a driverless car is perfect at navigating scenarios it has previously handled safely"... The foundations of this article's argument are not nearly as sound as the author seems to think.
Hands up who wants to trust their health to the untested assertions of a pharmaceutical company
Well, that depends. Do I have a mild case of acne, or am I dying of cancer? My willingness to try an untested drug is likely to be very different in those two scenarios.
When cancer kills someone, you can't sue cancer.
If a driverless car kills someone, the car maker is the only one I can think of who would be responsible. A passenger who wasn't driving can't be responsible. So legally the insurance needs to cover this. If they can't be insured, they can't be on the road.
I'm not sure if I expressed that point well, but what I was meaning was that the car makers will have to accept the blame if they're going to be selling cars that do the driving (or more precisely, take the burden of the blame for bad driving).
As an aside, to muddy the waters even more, I'd say even if the car gets hacked and made to kill someone, the car maker might still be legally responsible. It's a minefield for sure.
If the car's software is defective, the company should clearly be held accountable.
Each update will need to be tested and approved for safety for every vehicle it needs to run on.
Also companies will understandably be unwilling to share their data with competitors, and the data is probably not translatable between companies anyway.
Plus, a bad pharmaceutical drug only harms the user, a dangerous car on the road is dangerous to people who don't want them.
I think those decisions are necessary are driverless cars but will start a huge discussion about the ethic behind calculation the minimum victim. This includes making decision if saving a child is more importing than saving a elderly.
Collectively, the death toll of driving will be significantly reduced, but it will only take a few people being killed by driverless vehicles for people to make a fit about it, because there is a clear victim.
In an accident, it's exactly that: an accident. It wasn't an intended decision, it just sort of happened. With AI and autonomous vehicles, everything is a decision, and someone gets the worse outcome, and every little bad thing that happens is going to cause an uproar.
I'm so sure that something similar has happened before, I'm struggling to come up with it though.
Some older statistics I read claimed that (in UK I think) 30% of crashes were due to alcohol and another 30% to fatigue. In these cases for example there is a culprit and the crash was no accident. For me, accidents are cases when a mechanical part breaks or an oil spill makes the vehicle incontrollable. But people crashing into each other because of alcohol, fatigue, boredom, distraction or speed should be responsible for their acts and should not claim being in an accident.
I think that one of the issues is that it's often not just an accident, not something that "just sort of happened". Safe driving practices do work. E.g. checking your blind spot, not running stop signs, always looking both ways before going when the light turns green, etc. Of course, you can only do so much to protect yourself against other people's bad driving. But there is a moral component to car accidents; they happen more often to bad drivers.
We may not like it but that's how the public will see it.
The answer really sometimes is "you are out of luck".
For a bug or a really bad known issue, authors and designers (car company) should be liable.
Just look all the civil liberties and privacy that we have given up over the last 15 years in exchange for "safety" and being connected through social media and the internet in general.
If you would have told someone 20 years that we were going to start making teachers wear body cameras to record every word and movement of everyone they interact with, they would thought you were crazy, yet here we are.
So really, the only question comes down to, what's the ethical approach to deciding how an AI should prioritize human life? If a driverless car is forced into a situation where it must kill one of several people, who dies? (in practice that probably comes down to figuring out which action is the least likely to result in a fatality, even if all actions are extremely likely to result in one they're not going to have identical probabilities) And perhaps more interestingly, if the car has to decide between probably killing its driver, and probably killing someone else, which way does it decide? (though again, this probably comes down to which person is more likely to survive the accident, and that's probably going to be the driver because they're protected by multiple safety systems whereas someone walking along the road is not)
The only important part is that the driver is informed how the car may react in terms of the strategy and that the decisions of the driving system are recorded.
Literally all a driverless car has to do is hit the brakes if it's going to hit an obstacle. There's no moral decisions, no discussions about who deserves to live and who should die. Just use the brakes.
I just wrote the code. And it's open source so any car company is free to use it. Here it is:
if (obstacle) then { brakes = true }.
You're welcome.
As a back of the envelope calculation, I was with you until that sentence. That is an unwarranted and very aggressive assumption.