And this is the beginning of the end of bus driving as a profession. Sure, this is in well defined, short (and private) routes. First Santa Clara, then Stanford shuttles, then airport shuttles, then Googlebus drivers.
Enjoy the raises while you can.
They are developing platforms that will operate inside contained environments. What you are referring to is very different from what they are doing. An autonomous vehicle that operates on a public road faces much more challenges than one that does so in a contained environment. While working on my own autonomous car (yes, I bought a car for the sole reason to try and do this), I realized that the simplest route would be to do as they did. It can operate in a closed loop, similar to line following robots. Eerily similar to automated trains in airports. Its a challenge to build a safe autonomous vehicle, a bit less so in the way they are doing it. Not trying to diminish their efforts though. I have first hand experience of how hard this simpler approach is.
No doubt it is hard, our previous experience helped us a lot, we did make a fresh prototype vehicle in USA in just 2.5 months including procurement. Working with newer sensor and writing different perception algrithmso for current use case and even we used a different motion planning approach. We never got stuck anywhere, the only problem is time vs skilled manpower. We just wish we could have more people in our team to build more features sooner and ironing out more corner cases which have not prioritized due to lack of time. There are so many module and so many things we want to improve, and we know how, just need few more hands.
We our-self feel very proud to have been able to come to USA, hire interns, get the basics of every module right enough and integrate on time, including getting drive by wire and other retrofitting done and tested and stated piloting completely autonomous in unimaginable short time frame, thanks to the push from YC partners.
One obvious question, why aren't more subways fully automated? It's not like they can't implement remote control override for emergency situations... Is it still a psychological issue (with riders)?
Automatic new line are easy but it's harder to automatize old line without interrupting traffic. It has been done for line 1 in Paris between 2007 and 2011 (https://en.wikipedia.org/wiki/Paris_M%C3%A9tro_Line_1) but all other old line in Paris have still not been automatized.
Because most subways run on legacy infrastructure that would be difficult to upgrade/replace. RF repeaters for emergency remote control for example would need to be installed, certified and thoroughly tested.
Given that drivers aren't a big cost centre for subway operations in comparison to maintenance etc. the cost/benefit doesn't make sense.
I think the pensions are a sizable part of their expenses. If they automate their retired workforce age out and there is no endless retirement pool to contribute to. So this would be a significant savings.
The first fully automated subway line was in New York, in 1959. The Times Square - Grand Central shuttle was fully automated for six years.[1] But, per union rules, they still had someone on board. A major platform fire at the 42nd St station damaged the rolling stock, and when the station was rebuilt, the one-off automated system was not rebuilt.
The main reason for trying it on that line is that the trip is very short, and the train reverses at each end. The train operator's walk though the train to get to the other end caused delays. Paying for two drivers, one at each end, was a bit much.
They will be. I was thinking of this earlier today, and there is still some coordination between schedules, doors closing with people still trying to get on, etc. etc. In Sydney, you still have people blowing whistles to signal to the driver that it is safe to close the door and go.
I'm wondering if that is maybe a more difficult problem to solve than driving. In driving, you know the direction cars 'should' be going, you need to account for lane changes and turns, etc. but for the most part they are expected. I think in an open environment people are much less predictable in their movements.
In metro systems, 50 percent of service affecting failures come from passenger exchange. Majority of the remaining failure come from vehicle failures. Failures due to driving mistakes are very few.
Passenger flow management is the hard part of automated mass transit for performance. It has to be safe yet efficient. It's indeed surprisingly difficult.
Comments
And this is the beginning of the end of bus driving as a profession. Sure, this is in well defined, short (and private) routes. First Santa Clara, then Stanford shuttles, then airport shuttles, then Googlebus drivers. Enjoy the raises while you can.
They are developing platforms that will operate inside contained environments. What you are referring to is very different from what they are doing. An autonomous vehicle that operates on a public road faces much more challenges than one that does so in a contained environment. While working on my own autonomous car (yes, I bought a car for the sole reason to try and do this), I realized that the simplest route would be to do as they did. It can operate in a closed loop, similar to line following robots. Eerily similar to automated trains in airports. Its a challenge to build a safe autonomous vehicle, a bit less so in the way they are doing it. Not trying to diminish their efforts though. I have first hand experience of how hard this simpler approach is.
No doubt it is hard, our previous experience helped us a lot, we did make a fresh prototype vehicle in USA in just 2.5 months including procurement. Working with newer sensor and writing different perception algrithmso for current use case and even we used a different motion planning approach. We never got stuck anywhere, the only problem is time vs skilled manpower. We just wish we could have more people in our team to build more features sooner and ironing out more corner cases which have not prioritized due to lack of time. There are so many module and so many things we want to improve, and we know how, just need few more hands. We our-self feel very proud to have been able to come to USA, hire interns, get the basics of every module right enough and integrate on time, including getting drive by wire and other retrofitting done and tested and stated piloting completely autonomous in unimaginable short time frame, thanks to the push from YC partners.
I grant you that. But this is the beginning.
One obvious question, why aren't more subways fully automated? It's not like they can't implement remote control override for emergency situations... Is it still a psychological issue (with riders)?
Automatic new line are easy but it's harder to automatize old line without interrupting traffic. It has been done for line 1 in Paris between 2007 and 2011 (https://en.wikipedia.org/wiki/Paris_M%C3%A9tro_Line_1) but all other old line in Paris have still not been automatized.
Because most subways run on legacy infrastructure that would be difficult to upgrade/replace. RF repeaters for emergency remote control for example would need to be installed, certified and thoroughly tested.
Given that drivers aren't a big cost centre for subway operations in comparison to maintenance etc. the cost/benefit doesn't make sense.
I think the pensions are a sizable part of their expenses. If they automate their retired workforce age out and there is no endless retirement pool to contribute to. So this would be a significant savings.
The first fully automated subway line was in New York, in 1959. The Times Square - Grand Central shuttle was fully automated for six years.[1] But, per union rules, they still had someone on board. A major platform fire at the 42nd St station damaged the rolling stock, and when the station was rebuilt, the one-off automated system was not rebuilt.
The main reason for trying it on that line is that the trip is very short, and the train reverses at each end. The train operator's walk though the train to get to the other end caused delays. Paying for two drivers, one at each end, was a bit much.
[1] http://www.nycsubway.org/wiki/IRT_Times_Square-Grand_Central...
They will be. I was thinking of this earlier today, and there is still some coordination between schedules, doors closing with people still trying to get on, etc. etc. In Sydney, you still have people blowing whistles to signal to the driver that it is safe to close the door and go.
I'm wondering if that is maybe a more difficult problem to solve than driving. In driving, you know the direction cars 'should' be going, you need to account for lane changes and turns, etc. but for the most part they are expected. I think in an open environment people are much less predictable in their movements.
Thoughts?
In metro systems, 50 percent of service affecting failures come from passenger exchange. Majority of the remaining failure come from vehicle failures. Failures due to driving mistakes are very few.
Passenger flow management is the hard part of automated mass transit for performance. It has to be safe yet efficient. It's indeed surprisingly difficult.
But there are a few fully automated lines. The Taipei brown line is fully automated, granted its not the highest volume line, but still very busy.
Id say yes, it is entirely psycological, it should be doable now.
I see it not as the beginning, but as another step. People movers aka horizontal elevators have been used for decades (https://en.m.wikipedia.org/wiki/People_mover)
Yes, they are less flexible because they need a fixed track, but this is just a step that loosens the "well defined" part.