Where's the lane? Self-driving cars confused by shabby U.S. roadways
reuters.com
reuters.com
(I'm not a lawyer, but "We created an optical illusion directing people to crash into a wall, so those victims should have been paying attention and figuring it out" doesn't strike me as a robust defense in court.)
the state of the roads isn't what is stopping self driving cars. considering the amount of road construction going on at any one time no amount of markings are going to help, then toss in rain, bad lighting, and snow.
No, what is holding them back is the programming and processing power that cars are expected to mount. As humans can drive with on their sense of sight cars will have the advantage of sight that see in conditions people cannot plus also have maps available at all times which should give guidance on where the roads really are.
The roads are deteriorating foil is typical election year crying. the bridges and roads are much improved since the 90s and the key fact most writers and readers of these articles don't understand is, the federal government does not have domain over many of the roads that need maintenance.
The autopilot will look for lane markings or road surface edges, but seems to favour following the vehicle in front where possible. This especially helps drive better in rainy weather where road markings are obscured by reflections.
https://en.wikipedia.org/wiki/Barra_Airport_%28Scotland%29
It does have scheduled flights - but the schedule has to take account of the tides.
Then we have to wish automatic cars have a Jeremy Clarkson mode
Point Road, Nelson was the one that really caught me out though. It looks significantly different between Satellite and Map modes: https://www.google.co.nz/maps/place/Point+Rd,+Monaco,+Nelson...
Frankly, US roadways are really good. I was amazed by the amount of signage present, not to mention the pavement itself.
Yes there are imperfections. But when was the last time you tore apart your car's axle due to inability to avoid the 20th gaping hole you ran across in just one way of your commute?
You want shabby roads? Go to third world countries. That's the real test for self-driving cars.
I myself compare the United States with our peers in Western Europe, Japan, Korea, etc. In this scope, our roadways are actually kind of sad, especially when you factor in how much we spend on them and double-especially when you factor in that we don't have solid railroads.
Our highways are generally paved really thin (compare to: German highways) and they end up cracking and breaking all the time. I've never driven between two cities on an Interstate highway without being slowed down by construction work.
Also, just from day to day observation: I live in Chicago and everywhere I walk, the streets look disastrous. They're broken apart, and some of them are half-repaired with concrete chunks sticking out (check out LaSalle and Randolph)--on some streets it's a miracle to me some cars get through without a flat tire.
We are a tremendously successful and advanced country. There is clearly a very big problem with the state of our roads.
I think you mean 'passenger railroads'. The US freight railroad is world-class. Lots of spurious debate about railroads in the US comes from confusing the pros and cons of a freight network (which we have) with the pros and cons of a high-speed passenger network (which we don't have). The benefits of a continent-sized high-speed rail network in a continent with low population density tends to be over-emphasized.
As for benefits/needs of a high speed passenger network--all I have to say is that my current options for going Chicago - New York which I do frequently are: 1. garbage airlines that are consolidating more and more and increasing their prices for no apparent reason, 2. broken roads that are constantly being repaired, and 3. Amtrak
That said, it's clear to me that a high speed rail connection (for example Chicago - NY at ~200mph) would be a no brainer. I'd even pay more than I pay American Airlines for the route.
So, instead of worrying about continent-sized high-speed rail networks, maybe we should start by thinking about building a high-speed rail network that spans the Eastern Seaboard states, where so much of the population is packed, then then expand out from there (Chicago, Memphis, New Orleans, Houston, etc.). We've already tried this with Amtrak and their Acela Express, but it's kinda lame: expensive and not that fast.
If we just built a seriously fast high-speed train between Boston and DC (stopping at NYC, Philly, and Baltimore along the way), and priced it competitively with air travel, then we'd be getting somewhere. Extend it down to RTP, Atlanta, and Florida next, and then a western spur to Cleveland and Chicago.
A separate high-speed rail network along the west coast, linking San Diego, LA, SanFran, Portland, Seattle, and Vancouver would also make a lot of sense.
What probably wouldn't make so much sense is trying to link the east and west coasts with such a system. Rail (even HSR) is just too slow to compete with air travel for distances that far.
Of course, Musk's Hyperloop idea might make more sense than any of this, though it'd basically be serving the same purpose in mostly the same way, just with tubes instead of rails. But its speeds would be even higher than air travel, so it could really replace air travel for major corridors, leaving air travel for places where Hyperloop isn't built yet, or for any travel which crosses large bodies of water.
For long distances, yes. For short to medium distances, high-speed rail can be much better. In the DC-Boston corridor, rail is already very competitive with air and that's with "high-speed" rail speeds averaging 80mph. True high-speed rail would be much better than air in that corridor.
Not in the context of self-driving cars. For that, US roads should be good enough. If they aren't why not just provide roads that are prepared with aids (electronic or otherwise) just so self-driving cars will work properly?
I was simply responding to someone defending US roads when there's a publicly visible crisis happening with our road (among other) infrastructure that no politician seems to want to address.
You can replace "exploring other planets" with poor roadways, wealth inequality, or whatever else you would like.
[0] http://www.northcountrypublicradio.org/news/story/31231/2016...
I've often asked that myself dear robot. Welcome, you're now truly a fellow driver
There is a spot on the 405 S around Culver City that this used to happen regularly to me at.
If it's not clear, 2 lanes come over the overpass towards where I shot the photo from. An offramp from 101 North terminates where the white pickup is.
This has always been a terrible merge. 2 lanes come across the freeway, and the offramp is a new 'added' lane, but the striping/bott's dotts between the #1 and #2 lane coming down from the overpass are virtually nonexistent. There are cracks in the road (the dark marks) where the lane markings should be.
It was always a big risk because cars in the right lane coming over the overpass used to just drift over into the offramp's new lane, and half the cars coming down the offramp didn't know they had a new lane, so they'd just STOP at the end of the ramp.
THEN the City, in its infinite wisdom, decided to fix none of these problems, but instead add a striped bike lane that cuts across the offramp. Absent lane markings to follow, drivers in the right lane would just follow the dashed bike lane and force themselves into the offramp's new lane. I witnessed at least 5 near collisions in the several minutes I was there taking photos.
They've since SOMEWHAT improved the markings between #1 and #2 lanes, but the bike lane markings are much more substantial and people still tend to follow them. Also, it still tends to confuse people using the offramp.
But this is an endemic problem; I bike commute and often a bike lane switches sides of a car lane in the middle of an intersection. It's the traffic version of "Step 1: right lane. Step 2: ??? Step 3: Profit!" Or "good luck, hope you come out on the other side of the intersection alive.
http://www.openstreetmap.org/?mlat=37.51639&mlon=-122.25424#...
The photo is taken looking towards the freeway, showing the offramp.
A typical bike lane in the US is made out of paint, the lack of protection isn't noteworthy.
I assume the extra "markings" are related to a road repair, but I couldn't imagine a worse situation for a self-driving car.
1) Under rainy conditions?
2) Heavy snow fall?
3) Incompletely plowed roads?
4) Roads under construction - i.e. partially striped and the little flags that haven't been completely moved around between road realignments?
Do you mean to tell me Alpha Go can beat a human at Go but can't be trusted not to drive a car into a ditch?
It is nice to know that the way we avoid the singularity is with confused road markings :-)
edit Nevermind, I forgot that not all roads have an even number of lanes in both directions (even considering single turning lanes and medians). But absent a median or any markings at all, the above is a relatively safe bet. I'm sure they could build a set of heuristics to accommodate the exceptions.
Humans have spatial vision, so we should also be able to create cameras that can make out objects floating in free space (such as traffic lights), piece out their components, and compare them to a set of common criteria to determine its intent, the way humans basically do.
|0|1|2|3|
_| | | | |
/ / / /
_ / / / /
|1|2|3|
|1|2|3|
|1|2|3|
|1|2|3|
Unfortunately, the diagonals are marked incredibly poorly, so most drivers starting in lane N will go straight and end in lane N-1. So if you drive according to the law in lane 1, you would almost certainly get sideswiped eventually by someone going straight in lane 2.I suspect an AI driver would be astute enough to see the poorly marked lines, but most humans aren't! So the AI would frequently get sideswiped here.
Yes, but apparently self-driving systems are doing a worse job than humans. But this only means the AI isn't quite there yet. I say AI, not sensors, because their vision is probably already better than human's.
Edit: Also that company makes add-on collision detection products. That is a different application than auto-driving.
this is exactly the moment when I ponder "why the hell is this whole automatic-self-driving-car thing being pushed so hard generally?"
it seems like a rather absurd and silly effort to begin with... what's wrong with a bloody system of maglev propelled capsules being shot through tubes, or the train, or a normal car you drive with a steering wheel, accellerator pedal, and brakes?
http://www.bloomberg.com/news/videos/2015-01-06/rolls-royce-...
Most people in the industry are still expecting self-driving cars to be able to operate on normal roads in CA and some other favorable locations within 5ish years, which makes sense given the current state of the tech. In 6 years Google has gone from no self-driving car at all to many self-driving cars logging over 1.3 million miles with a single minor fenderbender of questionable fault. Given another 5 years to develop the tech, train the software, and expand the corner cases, there's no reason to think you won't be able to hail a robocab in San Jose in 2021.