Thanks to @vanshnook and Transit Talk NYC for helping us with our proposals. Please give this a read, as we have created a new proposal for a better 7 train extension and a better Northeastern Queens transit system.
This Post is from an account that no longer exists. Learn more
4
Replying to @joshuawolk
Does this factor in dwell times? I don't think shifting even more people onto an already crowded platform like Union Sq is good practice, just look at Roosevelt Ave during rush hour, where because of how many people get on and off here, it starts delaying trains.
64
Replying to @scottwfarrell @nicolegelinas
Our current setup is also interlining, except done in the worst way (reverse branching, which is why our trains are so delayed). Thru running isn't that.
Also, again, length is just a factor. Commuter Lines are way longer than subway lines, yet have a much higher on time rates.
34
Replying to @scottwfarrell @nicolegelinas
They are also deinterlined and have CBTC.
Length is a factor but it is not the end all be all when it comes to reliability and on time performance.
1
1
40
Oh, I absolutely care about these issues. But my question to you is why do you think Queenslink is "unwanted" and "unneeded."
2
103
Replying to @BRamkaran @The_Solo_Mans
And if that is not good enough, the translation is that every 5th to 6th train through this interlocking gets delayed. When there was a train every 2 mins on average through that junction, that is equivalent to one delay every 10-12 mins.
33
Replying to @BRamkaran @The_Solo_Mans
Because the MTA still tries to run the same number of trains and that junction still exists prior to 12/8.
Not the own you think it is.
25
Replying to @BRamkaran @The_Solo_Mans
Monday: Switch Problem
Tuesday: Mechanical Problems on the E
Wednesday: Broken Rail
Thursday: Signal Problem
How are these related to the swap again?
1
34
Replying to @The_Solo_Mans
And you are not going to play the one seat ride game when the 53rd St Tunnel is the preferred tunnel of F train riders, not 63rd St.
38
Replying to @The_Solo_Mans
That is your experience. Meanwhile, this is what a delay graph looks prior to the swap.
Furthermore, you are tracking delays that have nothing to do with the swap. A switch problem at 5/53 and a broken rail at QP would too also have screwed over pre-12/8 service.
2
57
Yeah because those are delays unrelated to swap. Like you put everything back and there are still going to be problems with how service delivered.
1
1
34
Replying to @BRamkaran
Still trying to frame this from an UES resident, who are not the majority on QBL, are you?
1
56
Replying to @BRamkaran
Paris Metro is completely deinterlined, Rome is as well, and Singapore is too. We are trying to bring the system in line with operational standards with other countries, and part of the reason why they are able to operate good frequencies is because of less choke points.
1
81
Replying to @BRamkaran
Yeah and London has way less interlining than NYC. Not to mention newer lines built around the world (including in London) has done away with the interlining concept.
2
1
45
Replying to @BRamkaran
It won't when you have to factor dozens of merge junctions and you are running trains at various frequencies.
1
1
63
Replying to @BRamkaran
Likely because of how bad the merging conflicts is and how the MTA left weird gaps to account for that. Let's see if that gets solved when the swap occurs.
1
28
Replying to @BRamkaran
Because why should they? The are hundreds of merging conflicts and hundreds of trains in the system. If the MTA starts to report on, how your E train is held because of a F train ahead, every train minus the non interlined ones would have an alert.
1
1
79
Replying to @BRamkaran
Now let's take one source of delays away, called merging conflicts. That is what the swap achieves and the majority of the delays comes from merging conflicts.
That is why the variability graph used an IQR, not a range, as that eliminates outliers via those other factors.
2
1
68



