Google Self-Driving Car Project  Monthly Report  July 2016 


      BUILDING IN LAYERS OF SAFETY IN A SELF-DRIVING CAR    Every device experiences glitches from time to time, whether it’s a cellphone, a computer, or even a  simple toaster. Naturally, people often ask us, what happens if something goes awry with the  equipment operating a self-driving car? Of course, the systems that power our self-driving cars need  to be more robust than your average household device, so we’ve built in many layers of safety and  protections. Our goal is to make sure our car can safely operate even if things don’t go according to  plan.    Our team is focused on making our roads safer, and that includes finding ways to make our car’s  internal systems as reliable as possible. On a practical level, we begin with strengthening the most  basic components of our self-driving systems — things like connectors and wiring harnesses that  enable our hardware and software to communicate. On our private test track, we simulate and 

  Google Self-Driving Car Project  Monthly Report  July 2016  prepare contingencies for all manner of potential faults: a loose cable in the hardware, a shorted  wire, loss of power, or a bug in the software.     On the road, our car performs thousands of hardware and software checks every second to ensure  that key components are working as intended. Because we’re constantly monitoring our system, our  cars are designed to detect an issue and determine whether it’s small enough to continue driving  (e.g. the tire pressure is low) or big enough to stop or pull over (e.g. a laser stops working).    We employ complementary sensors and software, so our car doesn’t rely on a single type of data to  drive. For example, our suite of cameras, lasers and radars work together to give our cars 360  degree visibility, so even if there’s a glitch in one camera, our cars can still safely pull over. Likewise,  our software uses a combination of algorithms that complement each other, so our cars don’t rely  on a single technique to detect others on the road and navigate safely.    For critical driving functions, we go a step further and build in fully redundant systems. Arguably the  most critical function in any kind of car is the driver. In today’s cars, a backup human can’t be  installed to immediately take over if the driver is tired or distracted (despite the best efforts of  backseat drivers!). In contrast, each of our self-driving vehicles is equipped with a secondary  computer to act as a backup in the rare event that the primary computer goes offline. Its sole  responsibility is to monitor the main computer and, if needed, safely pull over or come to a  complete stop. It can even account for things like not stopping in the middle of an intersection  where it could cause a hazard to other drivers.     With layers of safety and redundant systems, we can develop a fully self-driving car that doesn’t  need to rely on a human as backup if something goes wrong. Given that human error and distracted  driving are involved in 94% of crashes, this technology has the potential to make our roads  dramatically safer.  


    TRAFFIC COLLISIONS INVOLVING AUTONOMOUS FLEET    Given the time we’re spending on busy streets, we’ll inevitably be involved in collisions; sometimes it’s  impossible to overcome the realities of speed and distance. Thousands of minor crashes happen every day  on typical American streets, 94% of them involving human error, and as many as 55% of them go  unreported. (And we think this number is low; for more, see here.)    For collisions occurring in CA, the following summaries are what we submitted in the “Accident Details”  section of form OL316 Report of Traffic Accident Involving an Autonomous Vehicle. 

  Google Self-Driving Car Project  Monthly Report  July 2016    July 15, 2016: A Google prototype autonomous vehicle (“Google AV”) operating in autonomous  mode traveling westbound on Cuesta Dr. in Los Altos, CA was rear ended. The Google AV was  stopped at the stop sign at the intersection of Cuesta Dr. and Springer Rd. when a vehicle  approaching from behind in the same lane collided with the Google AV. The other vehicle was  traveling at approximately 7 mph when it struck the Google AV. The Google AV sustained minor  damage to its rear hatch and rear sensor. There were no injuries reported at the scene.        


  Buzzfeed: Old People Ride In Google’s Self-Driving Cars For The First Time  Fortune: Google Self-Driving Cars Have Learned How to Interpret Cyclists' Hand Signals  Washington Post: As driverless cars grow closer, a delicate balance between rules and  guidelines  San Francisco Chronicle: Photographic proof that driving in Calif. is more dangerous than  ever #drivingselfie 

Google Self-Driving Car Project Monthly Report

Jul 15, 2016 - On the road, our car performs thousands of hardware and software checks ... It can even account for things like not stopping in the middle of an ...

530KB Sizes 1 Downloads 56 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.