Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Google's self-driving car gathers almost 1 GB/sec

twitter.com

Post reply on HN
Print view View original

31–40 of 77 posts

Re: Google's self-driving car gathers almost 1 GB/sec

#31

Post by beambot »

Game_Ender wrote: post #23

He is off by an order of magnitude. The Velodyne 64 on that car only has a 100 Mbit connection [1]. Each of the 5-10 radars on that vehicle is connected over a 1MBit CAN bus [2]. The front facing is almost definitely a Gigi-E or Firewire camera so it's at most 1000MBit. Doing the math: 100 + 10*1 + 1000 = 1100MBit != 8192Mbit (1 GB) 1. http://velodynelidar.com/lidar/products/brochure/HDL-64E%20S... 2. http://www.kvas…

If other robots I've worked with (eg. the PR2) are any indication... 1GB/sec. is probably on the low end for the total data throughput. The PR2 had a high-res camera (GigE?), quad stereo cams in head (narrow and wide FoV), dual "wrist" cameras, a Kinect (usually), dual Hokuyo UTM LRF's, full 14+ DoF kinematics at 1KHz, and lots and lots of diagnostic info (eg. "heartbeat", system diagnostics, localization signals, IMUs, etc).

Granted, we didn't log all that data all the time, but TL;DR: I wouldn't nitpick over a factor of 8 based on your own calculations.

Re: Google's self-driving car gathers almost 1 GB/sec

#32

Post by conductor »

Computers get hacked evey now and then, I predict software assassinations in the future, i.e. somebody hacks into a self-driving car, installs a software component which will be activated at some point (i.e. when it identifies a specific car/human and crash into it). Then it can auto-destruct, no evidence left. I ask, who will be responsible?

Re: Google's self-driving car gathers almost 1 GB/sec

#33

Post by mseebach »

jkldotio wrote: post #22
salman89 wrote: post #11

What are things city planners can do from an infrastructure perspective so that we can drop the amount of data that needs to analyzed in real time? For example, can we use special paint for road lines in order to make the cost of detection of road lanes lower?

I can't imagine many too many cases where they'd be useful in everyday situations because if the car can't handle everyday situations then it's not going to be a good car and is going to sink to the "we're concerned for safety" lobbying that rivals will engage in to ban it off the road until they've caught up. Perhaps QR-code machine readable parking with the available hours, that'd be useful even without self-drivin…

The purpose of most signage and road lines is to decrease ambiguity (Are there three or four lanes here? Which is better for a left turn?) and increase throughput safely. If signage could be made less ambiguous in such a way that self driving cars benefit, that's a good thing.

I think, however, that such a scheme should be based on single point of truth, ie. no QR-codes: The signage that a human can read should be the same that the computer can read.

Re: Google's self-driving car gathers almost 1 GB/sec

#35

Post by ari_elle »

kamkazemoose wrote: post #30
ari_elle wrote: post #21

Earlier quoted context omitted.

I can't believe that you were willing to abbr. "Google" with "GOOG" but had to use "almost" in this sentence (utterly redundant word here) or "1 GB/sec" instead of "1 GB/s" Sorry, i don't know how much "effort" you put into your abbreviation but your title looks like a dirty hack, i would never want on the front page. Google Car gathers 1GB/sec. What it "sees" making Left turn That would have been better in my opinio…

I don't think you can leave out the self-driving car. 'Google Car' is ambiguous and could mean either the Google Streetview cars or their self-driving cars.

If you think so:

-) Google Self-Driving Car gathers 1GB/s. Picture of it analyzing left turn

-) Google Self-Driving Car gathers 1GB/s. What it "sees" making Left Turn

My critic is not so much with the title op chose, more so that he/she felt the need to make the case that a Mod shouldn't have changed it.

Op wanted to know why it is Mod did it, i answered.

Re: Google's self-driving car gathers almost 1 GB/sec

#36

Post by piyush_soni »

conductor wrote: post #32

Computers get hacked evey now and then, I predict software assassinations in the future, i.e. somebody hacks into a self-driving car, installs a software component which will be activated at some point (i.e. when it identifies a specific car/human and crash into it). Then it can auto-destruct, no evidence left. I ask, who will be responsible?

Probably find the hacker? Just like what we do right now ...

Re: Google's self-driving car gathers almost 1 GB/sec

#37

Post by DasIch »

dsl wrote: post #10
DasIch wrote: post #5

Does anyone know what happens with this data? Obviously it is analyzed in realtime for driving but is it also stored for machine learning purposes? Is that data shared so that other cars can take advantage of it?

It's 1 GB/sec of data from sensors. Likely processed, but not stored. To get 1 GB/sec write throughput in a moving car you would need to be using some form of solid state storage, which would be pretty darn pricey over an hour test drive.

You only need to store the data until you can upload it, which might not be that long if the car has an internet connection. Furthermore I assume not all parts of that data is equally valuable. If this is raw data coming from sensors I think it is fair to assume that a significant part is noise that can be discarded.

So I would assume that even though you are probably unable to store 1GB/s of data - today at least - you might still be able to store the interesting parts and use those.

Re: Google's self-driving car gathers almost 1 GB/sec

#38

Post by DasIch »

piyush_soni wrote: post #36
conductor wrote: post #32

Computers get hacked evey now and then, I predict software assassinations in the future, i.e. somebody hacks into a self-driving car, installs a software component which will be activated at some point (i.e. when it identifies a specific car/human and crash into it). Then it can auto-destruct, no evidence left. I ask, who will be responsible?

Probably find the hacker? Just like what we do right now ...

You are assuming detecting manipulation is straightforward or even possible. What if someone is able to MITM software updates?

Re: Google's self-driving car gathers almost 1 GB/sec

#39

Post by vowelless »

beambot wrote: post #31
Game_Ender wrote: post #23

He is off by an order of magnitude. The Velodyne 64 on that car only has a 100 Mbit connection [1]. Each of the 5-10 radars on that vehicle is connected over a 1MBit CAN bus [2]. The front facing is almost definitely a Gigi-E or Firewire camera so it's at most 1000MBit. Doing the math: 100 + 10*1 + 1000 = 1100MBit != 8192Mbit (1 GB) 1. http://velodynelidar.com/lidar/products/brochure/HDL-64E%20S... 2. http://www.kvas…

If other robots I've worked with (eg. the PR2) are any indication... 1GB/sec. is probably on the low end for the total data throughput. The PR2 had a high-res camera (GigE?), quad stereo cams in head (narrow and wide FoV), dual "wrist" cameras, a Kinect (usually), dual Hokuyo UTM LRF's, full 14+ DoF kinematics at 1KHz, and lots and lots of diagnostic info (eg. "heartbeat", system diagnostics, localization signals, IM…

Agree. The point cloud in the self-driving car itself is probably on the order of 1/4 to 1/2 gig a second.

Re: Google's self-driving car gathers almost 1 GB/sec

#40

Post by Game_Ender »

beambot wrote: post #31
Game_Ender wrote: post #23

He is off by an order of magnitude. The Velodyne 64 on that car only has a 100 Mbit connection [1]. Each of the 5-10 radars on that vehicle is connected over a 1MBit CAN bus [2]. The front facing is almost definitely a Gigi-E or Firewire camera so it's at most 1000MBit. Doing the math: 100 + 10*1 + 1000 = 1100MBit != 8192Mbit (1 GB) 1. http://velodynelidar.com/lidar/products/brochure/HDL-64E%20S... 2. http://www.kvas…

If other robots I've worked with (eg. the PR2) are any indication... 1GB/sec. is probably on the low end for the total data throughput. The PR2 had a high-res camera (GigE?), quad stereo cams in head (narrow and wide FoV), dual "wrist" cameras, a Kinect (usually), dual Hokuyo UTM LRF's, full 14+ DoF kinematics at 1KHz, and lots and lots of diagnostic info (eg. "heartbeat", system diagnostics, localization signals, IM…

That was an upper bound to show the absurdity of his non sourced "fact". The reality is much lower because the main sensor is the Velodyne, and it only produces 5-6MB/s. The primary focus of his picture is the Velodyne point cloud. Which he says is "1 GB per second" which is 100 times larger than it really is.

I have worked on several fully autonomous vehicle projects based on Velodynes and their processing and logging rates are around of 5-20MB/ (as you would expect) so seeing someone quote "1 GB/s" is pretty awful.

Post reply on HN