Self-Adapting Traffic Lights
Roland Piquepaille writes "If you're like me, I bet you hate moments when you're in a hurry and all the traffic lights seem to intentionally switch to red just in front of your car. Now, according to Nature, a Belgian traffic researcher thinks that traffic lights that respond to local conditions could ease congestion and reduce your frustration. His method would not give you the individual power to switch the light to green. But if you were part of a group of cars approaching a red light, inexpensive traffic-flow sensors would detect your group in advance and turn the light to green. His simulations show that such adaptive traffic control is 30% more efficient than traditional ways of regulating traffic. However, his system has not been adopted by any large city. So you'll continue to be frustrated by these ?%&$! traffic lights for a while. You'll find more details and references in this overview."
His simulations show that such adaptive traffic control is 30% more efficient than traditional ways of regulating traffic. However, his system has not been adopted by any large city
I'll guess that the reason why is because a simulation shows this, not a real test. Traffic simulation has been a topic of much research, but as far as I'm aware, little convincing results have emerged... Simulations based on liquid flow do not work (they do not give anything like an average traffic), and those based on drivers modelization (ie, x % of 'aggressive drivers', y % of 'sloppy drivers', z % of 'careful drivers' etc) become incresingly complex and demanding with the scale of the simulation... I'm not aware of anything practical ever done with these (feel free to correct me).
In any case, if his adaptive system does work, it's a breakthrough. I've worked a few years back with people in charge of traffic and roads around Paris, and from what I've been told, nothing like this has ever worked better than static programming (with the exception of multiple programmings for different time of the day). From what I remember, even getting such programming right demands extremely experienced people. Of course, this might be specific to Europe where intersections are rarely perpendicular and often involve "creative" solutions.
I'm from a city in New Zealand (Hamilton) where we have a self monitoring system tied back to the City Council. Unfortunately it seems to be a little too smart, holding patterns that don't reflect the traffic. As a result, traffic changes its flow each day (drivers choose new routes) which further changes the trending and thus cancels the advantages you'd hope to gain. When the system is out or loops are cut (roadworks) the system reverts to timers/loops which seem to work better. Perhaps it's just when we add users the perfect system suddenly becomes imperfect...
It's nice to see a traffic signal enhancement that will actually make driving more efficient and direct rather than the opposite.
I do not deploy Linux. Ever.
Assume (for this post) that these devices actually work and improve the efficiency of city streets. This is why you can't find them on your block:
(1) Safety. A lot of effort is spent proving that a traffic control device is safe. When traffic lights screw up and allow opposing green lights, people die. It is entirely unacceptable for a traffic control device to screw up.
So when a city is faced with buying a proven design or a new advanced design that improves efficiency but may be a liability concern, the city will go with the proven design.
I concede that the new system would be tested endlessly, but I claim that any complex system will have flaws that don't show up until deployed in the field. I've seen unbreakable unix systems crash. It happens.
I think that provable safety in this application can (and will someday) be done. I just wouldn't want to be the first city adopting it.
So another option to ensure safety is redundancy such as that used in some airplanes. That is, multiple independant systems working on the traffic problem, and if any of them fail the others will notice. Doing this right costs money, which brings us to point 2.
(2) Cost. My city really doesn't even bother fixing road problems. I went to Berkeley CA the other day and they had enormous potholes that were "fixed" by painting bright colors around them so they could be avoided. If Berkeley doesn't want to spend a couple bucks to patch a hole, then why would your little town bother to consider removing existing systems that cost hundreds of thousands of dollars and replace them with ones that probably cost more?
Further, why would you want your city to spend this money for a marginal improvement in flow? The answer is because some intersections are so terrible that you always are caught up in traffic. These intersections are the bottlenecks that hold up everybody, ones where 30% improved efficiency would be a blessing, which brings us to the 3rd point.
(3) This doesn't help the worst intersections. This switching system would be nice for those pesky lights in your neighborhood that always seem to be red when you arrive, and that you are always first in line and usually the only one to go through in your direction.
I claim that the intersections which could use a 30% improvement the most are those that would not be helped by this system. That is because no matter which side is getting green, every precious second of green light is being used by traffic. This is 100% efficiency, as measured by throughput / theoretical maximum throughput. You can not improve this system by watching for groups of cars, since there are always groups of cars coming.
This would be a neat feature on some intersections, but these intersections aren't the ones that DOT really focuses on improving. The effort involved in making small intersections intelligently switch lights isn't generally worth the cost of doing so.
That said, I'd like to see this in use in my neighborhood, and I'm glad that people are looking into solving traffic congestion problems.
Yet it never seemed to occur to you to just obey the speed limit...
The thing about timed streetlights is that they're calibrated for a given speed. If they're, say, calibrated for 30mph and they're 1/4 of a mile apart, they'll turn green every 30 seconds regardless of your speed. If you go "only" 5-10 MPH faster... you just catch a red light, and still don't get home any faster than someone who obeys the speed limit.
I.e., you'd think people would get the idea already that there is really no reward for endangering everyone around. Someone who stuck to the speed limit got home in exactly the same time, and obviously with less stress. Didn't need to use up extra gas accelerating and decelerating all the time either.
And yes, I do mean endangering. Due to the elementary physics fact that kinetic energy is proportional to the square of the speed, so is the braking distance. E.g., the speed difference between 50 km/h and 70 km/h is 40%, but the braking distance _doubles_.
Add poor visibility at night (you might not see a kid dashing to cross the street until he's in front of your beams), the driver _and_ everyone around being tired, etc, and I really _don't_ need people doing "only" 10mph over the limit at night.
And again, as you've noticed, it doesn't even get you home faster. It just makes you stop at the next red light.
But naah... for some people speeding is like _the_ proof of their manhood. Obeying the traffic laws or not driving like an irresponsible maniac, that's like admitting sexual impotence. Or worse.
Geesh.
A polar bear is a cartesian bear after a coordinate transform.