Hacker News new | past | comments | ask | show | jobs | submit login

Accurate countdown clocks are hard, they by definition involve predicting the future which is widely accepted to be a Hard Problem :)

More specifically there are two major problems one of which is expensive to solve, and the other is impossible to solve.

The expensive one is providing and making use of lots of sensors so that we can have the best possible evidence on which to base our prediction. Most obviously we need to sense where the train is - the more accurately the better. But it's also valuable to know if the train is moving, and even if the previous platform is full of passengers who will board it before it can leave, or empty.

The estimates may prove wrong because of something as dramatic as a fault, or as trivial as somebody's coat trapped in the door.

London's system has always seemed fine to me, but it's noticeable that buses (for which London also provides countdown clocks) have much poorer accuracy, because as well as the vagaries of passengers they must contend with variable traffic. It only takes one idiot trying to reverse a lorry onto a major street to add 3-4 minutes delay to your bus and of course if you can't see the lorry you have no idea that's where the time went.

I don't agree that it makes sense to reduce the displayed precision as you suggest. The problem isn't with precision, it's accuracy, and you can't really fix that by reducing precision.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: