Google Self-Driving Car Project Monthly Report October 2015 

Activity Summary ​ (all metrics are as of October 31, 2015) Vehicles ● 23 Lexus RX450h SUVs – currently self-driving on public streets; 19 in Mountain View, CA, 4 in Austin, TX ● 25 prototypes – currently self-driving on public streets; 21 in Mountain View, CA & 4 in Austin, TX Miles driven since start of project in 2009 “Autonomous mode” means the software is driving the vehicle, and test drivers are not touching the manual controls. “Manual mode” means the test drivers are driving the car. ● Autonomous mode: 1,268,108 miles ● Manual mode: 938,621 miles ● We’re currently averaging 10,000-15,000 autonomous miles per week on public streets

Making sure our software won’t get spooked by vampires Halloween’s a great time to get some extra learning done. This week, lots of little ghouls, superheroes and even robots were running around Google with their families, so we asked them to hang out around our parked cars. This gives our sensors and software extra practice at recognizing children in all their unique shapes and sizes, even when they're in odd costumes.

We teach our cars to drive more cautiously around children. When our sensors detect children—costumed or not—in the vicinity, our software understands that they may behave differently. Children's movements can be more unpredictable—suddenly darting across the road or running down a sidewalk—and they’re easily obscured behind parked cars. So even if our cars can’t quite appreciate the effort the kids put in dressing as their favorite character from Frozen, they’re still paying full attention! ​

Google Self-Driving Car Project Monthly Report October 2015 

Why we’re aiming for fully self-driving vehicles As we see more cars with ​ semi-autonomous features​ on the roads, we’re often asked why we’re aiming for fully autonomous vehicles. To be honest, we didn’t always have this as our plan. In the fall of 2012, our software had gotten good enough that we wanted to have people who weren’t on our team test it, so we could learn how they felt about it and if it’d be useful for them. We found volunteers, all Google employees, to use our Lexus vehicles on the freeway portion of their commute. They’d have to drive the Lexus to the freeway and merge on their own, and then they could settle into a single lane and turn on the self-driving feature. We told them this was early stage technology and that they should pay attention 100% of the time -- they needed to be ready to take over driving at any moment. They signed forms promising to do this, and they knew they’d be on camera. We were surprised by what happened over the ensuing weeks. On the upside, everyone told us that our technology made their commute less stressful and tiring. One woman told us she suddenly had the energy to exercise and cook dinner for her family, because she wasn’t exhausted from fighting traffic. One guy originally scoffed at us because he loved driving his sports car -- but he also enjoyed handing the commute tedium to the car. But we saw some worrying things too. People didn’t pay attention like they should have. We saw some silly behavior, including someone who turned around and searched the back seat for his laptop to charge his phone -while travelling 65mph down the freeway! We saw human nature at work: people trust technology very quickly once they see it works. As a result, it’s difficult for them to dip in and out of the task of driving when they are encouraged to switch off and relax. We did spend some time thinking about ways we could build features to address what is often referred to as “​ The Handoff Problem​ ” -- keeping drivers engaged enough that they can take control of driving as needed. The industry knows this is a big challenge, and they’re spending lots of time and effort trying to solve this. One ​ study​ by the Virginia Tech Transportation Institute found that drivers required somewhere between five and eight seconds to safely regain control of a semi-autonomous system. In a ​ NHTSA study published in August 2015​ , some participants took up to 17 seconds to respond to alerts and take control of the the vehicle -- in that time they’d have covered more than a quarter of a mile at highway speeds. There’s also the challenge of context -- once you take back control, do you have enough understanding of what’s going on around the vehicle to make the right decision? In the end, our tests led us to our decision to develop vehicles that could drive themselves from point A to B, with no human intervention. (We were also persuaded by the opportunity to help ​ everyone​ get around, not just people who can drive.) Everyone thinks getting a car to drive itself is hard. It is. But we suspect it’s probably just as hard to get people to pay attention when they’re bored or tired and the technology is saying “don’t worry, I’ve got this...for now.”

Google Self-Driving Car Project Monthly Report October 2015 

Traffic Accidents Reported to CA DMV None for the month of October.

What we’ve been reading ● KQED TV (Panel discussion), “​ The Road to Self-Driving Cars​ ” (October 2015) ● KQED TV (Documentary), “​ Self Driving Cars: The Road Ahead​ ” (October 2015) ● Business Insider:​ Learning more about Google's self-driving cars made me terrified to ever drive again ​ (October 2015) ● MIT Technology Review, “​ Drivers Push Tesla’s Autopilot Beyond Its Abilities​ ” (October 2015) ● San Jose Mercury News, “​ Google, Tesla, Others Wait for DMV’s Self-Driving Car Rules​ ” (October 2015)

Google Self-Driving Car Project Monthly Report

Oct 31, 2015 - Making sure our software won't get spooked by vampires. Halloween's a great time to get some extra learning done. This week, lots of little ...

537KB Sizes 3 Downloads 69 Views

Recommend Documents

Google Self-Driving Car Project Monthly Report
Oct 26, 2016 - Our self-driving cars, on the other hand, can see a full 360 degrees ... to twist into a yoga pose to get a full 360 degree view of the road behind).

Google Self-Driving Car Project Monthly Report
Apr 7, 2016 - From residents to city leaders, tech-savvy Austinites have been supportive and ... I live near the Mueller area of Austin and I kept seeing self-driving cars drive ... personal element: in high school, I was involved in a serious.

Google Self-Driving Car Project Monthly Report
Dec 31, 2015 - ... to teach our cars to see through the raindrops and clouds of exhaust on cold ... As we're developing the technology, we've made sure our.

Google Self-Driving Car Project Monthly Report - googleusercontent ...
Mar 31, 2016 - Before we drive in a new city or new part of town, we build a detailed picture of what's around us using the sensors on our self-driving car.

Library monthly report -
Library monthly report. Generated on 2016-08-16T16:07:02.743Z. Book sales. Name. Author. Sales. A Tale of Two Cities Charles Dickens 351. The Lord of the Rings J. R. R. Tolkien 125. The Da Vinci Code. Dan Brown. 255. The Hobbit. J. R. R. Tolkien 99.

Monthly Report - December 2017 - Public.pdf
Store Count. New stores. December 2017. Norilsk-1 Miass-1. Moscow 3-1 Moscow 0-7. Moscow 0-12 Korsakov-1. Yeisk-1 Ekaterinburg-4. Shlisselburg-1 Usinsk-1. Tikhoretsk-1 Mirnyi-1. Podolsk-1 Novorossiysk-2. Blagoveshchensk-2 Arkhangelsk-1. Kazan-3 Orekh

Monthly Report - October 2017 - Public.pdf
Store Count New stores. October 2017. Ivanteevka-1 Bryansk-1. Naro-Fominsk-1 Nevinnomysk-1. Orenburg-1 Kingisepp-1. Stavropol-1 Naberezhnye Chelny-5.