Don't know if this has been discussed before, but can someone describe how the real time tracking for trains (available to us via departure vision) works? It woks reasonably well on "normal" days but is completely useless on 'bad' days. Today, for instance, Gladstone line was subject to 20-25 min delays in the morning. I was expecting the 7.15 departure from Murray Hill to NYP to be delayed given the preceding trains were all 20-25 min late. However, the app kept showing on time departure from all prior stations and arriving in MH at 7.13. When I got there, literally with a minute to go, the MH departure became 7.36. And that's when the train showed up. It was as if the train was stranded between Stirling and Gillette for 20+ min which wasn't the case. Are there specific points out the route enter the app can "true up" train status and then project forward?
I'm not sure how departure vision works from a technical standpoint, but I have seen similar issues that you've described while I'm using the app. Amazingly, some trains don't even show up on departure vision, or even the printed schedule. I took an "all stops to Hackettstown" from Hoboken one day around 4 pm. It apparently never made it to the printed schedule, and didn't show up on departure vision. It was not a holiday, so I'd guess that it was a scheduled train that made additional stops for some reason. That train crawled - an old diesel making every stop.
Frequently, trains that are late don't appear as late until they're *really* late. So, you'll see that 20 minutes out your train is on time, then within 6 minutes of the train due to arrive, it posts that there is a 35 minute delay.