4 ms·
Most, but not all of the time. There are dead segments in pretty much any system be it overhead or third rail. In which case you can assume the cars on those s
by CamperBob2 8y ago
Most, but not all of the time. There are dead segments in pretty much any system be it overhead or third rail.
In which case you can assume the cars on those segments are pretty much right where you left them, no? I'm assuming the name of the game is to optimize speed and spacing of cars on active segments.
Or do you mean the cars are basically coasting between segments under flywheel or battery power? Seems like dead reckoning is all that's needed to fill in those gaps. Maybe with a basic anticollision radar as a failsafe. :)
Nope. See Bill Wattenburg's demonstration with BART
I'm not familiar with him, and Google isn't helping much. Any good references?
It's a bit like automated driving.
Except there's no steering wheel, no pedestrians or cyclists, no weather or visibility problems, no uncontrolled vehicle traffic, and every bit of infrastructure is under your control at all times.
Hence my use of 'trivial' to describe the problem. Compared to what the folks at Waymo or Cruise have to deal with, the MTA and its contractors have no excuses whatsoever.
- inferiorhuman 8y ago> Or do you mean the cars are basically coasting between segments under flywheel or battery power? Seems like dead reckoning is all that's needed to fill in those gaps. Maybe with a basic anticollision radar as a failsafe. :) Assuming that the train hasn't failed, sped up, derailed, or found another reason to go into an emergency stop. You could make all sorts of assumptions but people typically like their train control systems to fail safe. > I'm not familiar with him, and Google isn't helping much. Any good references? Literally the first thing that comes up for "bill wattenburg bart" sums up the experiment pretty well. > Except there's no steering wheel True. > no pedestrians or cyclists On a subway? Jumpers or aggressors. On at-grade systems? Cars, bicyclists, pedestrians, wildlife, you name it you'll see it on the tracks. > no weather or visibility problems Weather is a huge issue for BART even underground, and I'd assume that goes more for the New York MTA. Weather is less of an issue now for Muni, but some of the equipment used to mitigate the weather routinely damages the train control equipment. If you're expanding your scope to longer distance rail traffic, look up what British Rail called "the wrong kind of snow". > no uncontrolled vehicle traffic You'd be surprised what a drunk driver is capable of. > and every bit of infrastructure is under your control at all times. Ideally. New York is an interesting mishmash of territorial pissing though. See also: Penn Station.
- CamperBob2 8y agoTo be clear, the scope of my comment is the problem described in the video. I literally know nothing about the details. I didn't understand the problem statement to encompass the incursion of snow, drunk drivers, or cyclists into the subway system, and I don't have any specific ideas on implementing a PTC-like system on a wide-area rail network. BART has a lot of surface coverage, so yes, I agree that many of those issues can't be hand-waved away in that case. But a municipal subway is, well, a municipal subway. The problem being discussed here is scheduling and tracking, not collision avoidance, obstacle sensing, or any of that other stuff. They are complaining that they can't implement rolling block scheduling because they don't know where their cars are or how fast they're going, and they're saying they need to spend an absurd amount of money to remedy that situation, and that's what I'm objecting to.
- inferiorhuman 8y agoBART has a lot of above ground track, but so does the New York MTA. With all of the above snow on the tracks will translate into problems underground. > hey are complaining that they can't implement rolling block scheduling because they don't know where their cars are or how fast they're going, and they're saying they need to spend an absurd amount of money to remedy that situation, and that's what I'm objecting to. Collision avoidance is an inherent part of scheduling and tracking. The reason they run so much distance between trains in New York (and almost anywhere else) is almost entirely because they're allowing enough distance for the train to stop without hitting the vehicle in front of it. Locating the vehicles with enough precision and accuracy is more than simply sending a signal — although the inductive loops used by Muni work well enough[1] underground until the trains (or, most recently, contractors) themselves destroy the loops. CBTC in by its very definition is more than simply vehicle location. While I'm mostly in the camp that BART is wildly incompetent, they tried to reinvent an even simpler train control in the 70s and demonstrated quite explicitly what happens when you underestimate the problem at hand. More recently they've spent tens of millions trying to come up with a CBTC (and so has Caltrain) and failed completely. If you know something they don't, talk to a lawyer and file some patents as you could make a mint. 1: For the first decade or so after Muni went to a CBTC[2] setup even something as basic as the transponders were huge pain points and you'd see massive failure rates over time leading to all sorts of problems underground. 2: The big selling point of the CBTC setup Muni chose was that it could be installed with a minimum of disruption AND that it used cheap, off-the-shelf parts. Alcatel/Thales abandoned that design almost immediately after pawning it off on Muni.