Live data from Hacker News

How traffic actually works

jliszka.github.io

151–160 of 186 posts

Re: How traffic actually works

#151
post #77

Earlier quoted context omitted.

OP here. That's a really good point. I just think the original article overreached in saying that zipper merging is a "simple cure" for traffic jams, without taking into account that the road might at or near capacity (and you hit capacity in a hurry when you lose a lane). My article doesn't account for variance in flow rates in congested traffic, but variance in car length (% of trucks on the road) might explain it.…

Isn't variance in flow rate the crux of the issue? Merge lanes are a special case in traffic, where another flow is entering the channel. This creates turbulence around the merge point that does not exist where there is pure laminar flow and all lanes can be treated equally. Would it help if "simple cure" was renamed as a "simple improvement?"

This.

Sure, there exists a point where the input flow is great enough that traffic must move slower. OP's entire argument is based off of this. The problem is that there are many things you can do to slow down the flow rate even further, and merging poorly creates this "turbulence" which wastes further flow.

And, it's clear that no improvement in merging behavior can beat the maximum road occupancy, however we can approach that limit much more closely.

I think that conceptually modelling traffic as fluid flows is quite clever, and the "turbulence" idea is particularly satisfying.

Re: How traffic actually works

#152
post #123
post #86

This article is so horribly incorrect and fails right at the very beginning with the wrong assumptions and a idea that isn't thought through. What the author forgot is to take by far the most important variable into account: SPEED So let's quote the author: "The important fact: there is a limit to the number of cars that can pass by a given point on the highway in a given amount of time, and that limit is one car eve…

> You can see on the right side how his "cars per second" is _exactly the same_ than on the left side. Is it my browser, or is this completely wrong? For me, the right side moves about double the amount of cars into the upper edge of the image. And I believe that this is the point of the section — it wouldn’t make any sense otherwise.

You are correct. And it's not just the images either, it's to illustrate the point that difficulty merging lowers the average flow-rate below that of "maximum lane occupancy".

Re: How traffic actually works

#153
post #118

Earlier quoted context omitted.

I'm sorry for the harsh critique. I think new radical ideas are great and people should question everything that's out there. But this way was not thought out well enough IMO. I hope you keep it up and maybe have a follow up post where you can fix some of the flaws. Some of your ideas are correct and noble. But always remember to take into account the real world driver and his/her behavioral flaws. Few thoughts: Inte…

Really appreciate the feedback, comes with the territory :) I added an update to the article looking at what happens when you vary the average car length (corresponding to the % of trucks on the road), fwiw.

> I added an update to the article looking at what happens when you vary the average car length (corresponding to the % of trucks on the road), fwiw.

That's silly, at most reasonable traffic flow-rates the difference in a couple of feet between a short car and a long car (esp with how uncommon the outliers are) is insignificant compared to the constant overhead of the per-car padding. And below reasonable traffic flow you're already at a high enough density to cause catastrophic traffic speeds.

Re: How traffic actually works

#154
post #123
post #86

This article is so horribly incorrect and fails right at the very beginning with the wrong assumptions and a idea that isn't thought through. What the author forgot is to take by far the most important variable into account: SPEED So let's quote the author: "The important fact: there is a limit to the number of cars that can pass by a given point on the highway in a given amount of time, and that limit is one car eve…

> You can see on the right side how his "cars per second" is _exactly the same_ than on the left side. Is it my browser, or is this completely wrong? For me, the right side moves about double the amount of cars into the upper edge of the image. And I believe that this is the point of the section — it wouldn’t make any sense otherwise.

Cars per second are the same. Open the two gifs next to each other. Each has 8 frames and the top right lamp is on for 4 and off for 4.

Re: How traffic actually works

#155

Earlier quoted context omitted.

For the record, I am "that guy" who runs all the way down to the end of the closed lane before merging over. Except I don't consider it an asshole move because as OP points out, I'm making the best use of the road ahead (while allowing fewer people to merge ahead of me) In interstate travel I have noticed the increasing frequency of the "two trucks" maneuver, in which a big rig driven by someone philosophically oppos…

I wonder if good zipper merges would be more likely to happen if, instead of having lane 1 merge into lane 2, both lanes got merged into lane 1.5.

Yes, that probably would improve things. I could totally see that working if we had electronic (or other quickly reconfigurable) lane markings.

Re: How traffic actually works

#156

Earlier quoted context omitted.

...following distance that the DMV tells everyone to observe... Who on earth leaves such a distance in stop-and-go traffic? I certainly haven't seen it. You might as well just assume that every driver will be safe, considerate, and wise.

If traffic is stop-and-go, a zipper merge is trivial.

Ummm, not in my experience.

Re: How traffic actually works

#157
post #101
post #92

Earlier quoted context omitted.

I think you're may be thinking of this as one mechanism instead of two separate mechanisms. You are dealing with a queue as well as a through-rate at the merge-point. The through-rate with one lane can still be 1/2 of the through-rate with two lanes, but because you have a queue waiting to reach the merge-point you can end up waiting much longer. More spacious merging will not change this because of the principle sta…

>Increasing the speed at the merge-point will not decrease the queue. It will only decrease the density of the queue but move it back further in traffic. Your time to cross the merge-point will be basically the same. I have to disagree with this. If you increase the speed at the merge point, someone who is newly joining the queue will definitely cross the merge point in lesser time than with lesser speed at the merge…

That doesn't matter though, as if they're going faster they're more spaced out. Only 2000 cars per hour can pass the merge point

Re: How traffic actually works

#158
post #2

That was the clearest explanation of traffic I've come across. I'm inclined to buy into it (often it seems no one knows what they're talking about when it comes to traffic). It also runs counter to what is commonly said about traffic jams. Most people focus on restoring smooth flow by doing things such as driving really slow to create space in front of you. This guy makes the case that "flow" is not really the import…

> For the record, I am "that guy" who runs all the way down to the end of the closed lane before merging over. Except I don't consider it an asshole move because as OP points out, I'm making the best use of the road ahead (while allowing fewer people to merge ahead of me)

Asshole move? I don't understand. I don't live in the US, but here it is encouraged to act like this! It's called a zipper merge. I remember public messages on the TV encouraging this behaviour, and there's road signs near merging lanes.

What's so asshole about this?

Re: How traffic actually works

#159
post #24

Earlier quoted context omitted.

Nobody is forcing you to stay in the congested lane. It was your choice and you have no reason to think everyone else has to do the same. If it's a legal lane, then drive in it.

That's fine if you can safely merge into the exit lane without slowing down traffic in the non-exit lane. Here's when it's not OK: cars in the exit lane are traveling at 2mph. You drive up next to the line, slow down from 55mph to 2mph and wait with your blinker on for someone to let you in. Now you've slowed a second 55mph lane down to 2mph, blocking thru traffic and creating a dangerous stoppage in the non-exit lan…

Have you blocked through traffic? Only if the number of cars per second drops. Also as there's going to be a queue of, say 1000 cars behind the merge point, it's better than the queue doesn't extend backwards into some other area of traffic, causing people who are turning off before the merge point to become involved in the slow traffic

Re: How traffic actually works

#160
post #51

Earlier quoted context omitted.

He's derived the fundamental diagram of traffic flow: https://en.wikipedia.org/wiki/Fundamental_diagram_of_traffic... . Up next: why F = ma really, really matters for space launches. Experts don't know this!

"1 weird trick for successful space flight"

Lockheed Martin hates this guy!
Post reply on HN