Self-Driving Cars and Organ Donation

Slate says: Self-Driving Cars Will Make Organ Shortages Even Worse. This will happen in two ways.

One, about 20% of US organ donations come from car accident victims. Presumably self-driving cars will reduce the number of organs available.

Two, a common place to opt-in to organ donation is at the DMV, while obtaining or renewing a driver’s license. Presumably self-driving cars will reduce the number of people who get driver’s licenses, and thus reduce the number of people who opt-in to organ donation.

The rest of the article is mostly about ways to improve the organ donation system in the US, irrespective of self-driving cars.

But it is an interesting case study a second-order effect autonomous vehicles will have on our world.

New Vehicle-to-Vehicle Communication Rules

Urban planner and historian Sarah Jo Peterson emails me that the US Department of Transportation just proposed a rule requiring automakers to include vehicle-to-vehicle communication hardware in new cars, and to use a common standard.

Of course, this is just a proposal. Before this could ever take effect, a new presidential administration will be in place and they might have their own views.

Peterson notes some concerns:

Are we moving to a world where bicycles need V2V and pedestrians need V2V? What does it mean for an act of mobility to require continuous government permission? (If you are not broadcasting, are you illegal? Will you be shut down in real time?)

I agree and would prefer if V2V arose as a de facto standard, instead of a de jure standard mandated by the government. This might be tougher for vehicle-to-infrastructure communication, which necessarily involves communication with government property, like traffic lights.

But if SMTP could rise as a de facto standard, the cause does not seem lost.

Meanwhile, Peterson points me to a Transportist blog post by David Levinson, arguing that in some scenarios, vehicle-to-vehicle communication may even be harmful in some scenarios.

The full blog post is hard to excerpt, but Levinson emphasizes that if we come to rely on vehicle-to-vehicle communication to navigate intersections (for example), a bug in the system or an unexpected event (he suggests a deer crossing the road) could bring traffic to a halt and possibly cause massive collisions.

I’m a little less pessimistic on that front, but Levinson is a professor of transportation and has been working on this problem for a decade, so I might defer to his logic.

How Ford Builds Autonomous Vehicles

Chris Brewer, the chief engineer for Ford’s Autonomous Vehicle Program, has a great post on Medium outlining the major components of Ford’s self-driving car.

Pay attention to the part where he talks about compute platforms and power consumption. That was my team!

Well, to make fully autonomous SAE-defined level 4-capable vehicles, which do not need a driver to take control, the car must be able to perform what a human can perform behind the wheel. Our virtual driver system is designed to do just that. It is made up of:

Sensors — LiDAR, cameras and radar

Algorithms for localization and path planning

Computer vision and machine learning

Highly detailed 3D maps

Computational and electronics horsepower to make it all work

It comes with a nifty video!

https://www.youtube.com/watch?v=6QJeaK7U87o

Should You Understand Backpropagation?

Backpropagation is a leaky abstraction; it is a credit assignment scheme with non-trivial consequences. If you try to ignore how it works under the hood because “TensorFlow automagically makes my networks learn”, you will not be ready to wrestle with the dangers it presents, and you will be much less effective at building and debugging neural networks.

That is from the excellent Andrej Karpathy, “Yes you should understand backprop”.

I say it’s possible to use deep neural networks quite effectively without truly understanding backprop. But if your goal is to specialize in the field and apply this tool to a range of problems, then “yes you should understand backprop”.

By the way, @karpathy is a prolific Twitter feed with 37,100 followers.

How to Become a Self-Driving Car Engineeer Talk

In November I gave a talk the Bay Area AI Meetup entitled, “How to Become a Self-Driving Car Engineer”. A fair bit of the talk was an overview of the Udacity Self-Driving Car Engineer Nanodegree Program. But we also touched on a variety of other topics related to autonomous vehicles, particularly during the question and answer session.

The slides for the talk:

The Lane-Finding demo:

The talk itself:

An interview I recorded after the talk with Alexy Khrabrov, the founder of Bay Area AI:

Thanks to the Bay Area AI team for having me!

Waymo

The Alphabet (Google) self-driving car unit is spinning out as a separate subsidiary within Alphabet, called Waymo.

This is not a surprise, because Google has been telegraphing this move for months.

That said, it’s not obvious what the practical implications of the move are.

TechCrunch speculates:

As an independent company under the Alphabet umbrella, Waymo will likely be less insulated from scrutiny regarding its progress and performance as a business, so its next steps in terms of partnership and sales or licensing model will be very interesting to watch.

It’s not obvious to me why that would be the case, unless Alphabet starts breaking out Waymo’s financial details in its annual reports. Alphabet hasn’t done that with other business units, though, so it seems unlikely they would do that with Waymo.

Eight Days of Autonomous Vehicles

December 14, 2016:

Uber has expanded its self-driving taxi trial to the home of technology and autonomous vehicles; San Francisco. Starting from 14 December, Uber customers with a credit card attached to a San Francisco billing address are eligible to ride in a fleet of five self-driving cars.

December 22, 2016:

“Our cars departed for Arizona this morning by truck,” said an Uber spokesperson in an email to The Verge. “We’ll be expanding our self-driving pilot there in the next few weeks, and we’re excited to have the support of Governor Ducey.”

The move comes after California’s Department of Motor Vehicles revoked the registration of Uber’s 16 self-driving cars because the company refused to apply for the appropriate permits for testing autonomous cars.

This does not feel like progress.

Startup Watch: Blackmore

A startup called Blackmore just raised a few million dollars to miniaturize sensors for autonomous vehicles.

A few interesting points about Blackmore:

  1. They want to embed lidar in the grill of a car. This seems like a difficult vantage point, since the sensor won’t have a 360-degree view of the environment.
  2. They plan to deliver prototypes next summer.
  3. Based on their website, they seem to target two markets: autonomous vehicles and the military.
  4. They’re based in Bozeman, Montana, which is a great town, but hardly a tech hub. Given the cost of housing in Silicon Valley, though, I’m tempted to apply for a job there right now.

Autonomous World

Business Insider recently launched a special series called “Autonomous World” that covers self-driving cars. It’s thorough!

Articles (I have not read all of them yet) include: