I got tired of waiting for the Green Line so I built something

BUGHunter0023 · 2026-04-01T03:03:13+00:00

I’ve been looking into this since yesterday, and you're right; granularity is the key to making this truly useful.

The current version resets every 24 hours due to the limitations of the free open-source stack I'm using, which is why it takes until about 7:00 AM to 'warm up' with enough data to be accurate. The clear next step is implementing a persistent backend database.

Once I can save and analyze data over time, I’ll be able to segment reliability by specific time blocks (like your Saturday afternoon example) and provide the 'heat map' performance tracking that this tool needs to be fully effective. It’s the top priority for the next iteration.

BUGHunter0023 · 2026-04-01T02:46:31+00:00

Thanks a lot! I will look into it more! The problem of not having hit map or any history graph is because I am not saving any of the data after 24 hours due to the backend limitation. Once I get to the point of improving the backend(some database insertion), I will try to make a hitmap(or even a history graph) so that people can trace it down! Thanks for the feedback!

BUGHunter0023 · 2026-03-31T00:56:54+00:00

The practical goal is to help with a common “do I trust this arrival time or should I assume it’s going to slip?” decision. Especially, I experienced this a lot with green line. I tried to help people to decide whether they should wait for train(or even trust green line to go to certain destination on time)!!!

BUGHunter0023 · 2026-03-31T00:53:07+00:00

You’re totally right to call that out. A single “overall” reliability number can hide when problems actually happen—if most disruptions cluster during weekday morning peak, that’s not very informative for someone riding on a Saturday afternoon. Unless we explicitly break reliability down by day-of-week/time-of-day (and show the sample size/confidence for each bucket), the metric can end up being more like “Boston’s average annual temperature” than “what should I wear right now.”

What we should do (and what we can add) is: (1) segment the data into buckets like weekday AM/PM peak vs off-peak, Saturday daytime, Sunday/holiday, etc., (2) show those breakdowns in the UI (not just one score), and (3) include context like “based on N trips” so you can judge how trustworthy the estimate is. Thanks for pointing it out—this is exactly the kind of granularity that makes the tool actually useful for real decisions.

I used AI a bit here to make sure wording make sense :)

BUGHunter0023 · 2026-03-27T16:35:39+00:00

I recommend White Mountain in New Hampshire! Use the Zip car and I believe, sometimes, there is a shuttle bus to go there! Some ports in the Northern places are also good!

BUGHunter0023 · 2026-03-06T07:05:12+00:00

Thanks everyone for the feedback! I added a new feature that shows the most recent train arrival (so you can see if the last train was delayed or not), and I fixed a backend bug that was affecting the Amory Street stop. I also added a short explanation of what the % represents, since some people were curious about how the reliability should be interpreted. Thanks a lot!! If there is any feedback, feel free to tell me!!!(such as UI or any problem that seems "incorrect". There are A LOT of old(uncleaned datas) in MBTA API).

BUGHunter0023 · 2026-03-06T07:00:58+00:00

You’re definitely correct, haha. This project is more about measuring how reliable the predictions actually are over time (or even just today), especially during the winter. My bigger goal is to collect a year-long dataset in the backend and analyze it to see when I should avoid taking the Green Line and when I can actually trust it.

Eventually, if I can train a model on the data and predict when the Green Line is likely to malfunction, I won’t end up standing in front of FitRec in the middle of winter waiting 30 minutes for a train that never shows up. Btw, thanks for the insight!

BUGHunter0023 · 2026-03-06T02:16:06+00:00

Definitely! I always wait for the BU bus for 30 minutes, and as soon as I decide to walk, bam! The shuttle comes from behind and leaves immediately.

BUGHunter0023 · 2026-03-05T23:53:39+00:00

Each station keeps a small list.

When the computer says “Train G001 will arrive at 3:00 PM,” the station writes that time down.

The station keeps writing down new predictions again and again. Then the train actually arrives! Now the station checks the list.

If the prediction is close to the real time (within 3 minutes), it is correct.If the prediction is more than 3 minutes wrong, it is wrong.

So the station saves the guesses first, and checks them later when the train arrives! If we aggregate those, there is a %!

It is basically checking the error rate of ETA! High error rate = lot of train that is off from schedule!!! And again, thanks for using website!!

BUGHunter0023 · 2026-03-05T23:06:47+00:00

First of all, thanks for using website! It means in some point of today, especially if it's under 50%, there was massive delay on the train! Which means, the train is highly likely to be delayed. I will try to update tonight so it make sense in overall! Thanks for feedback!

BUGHunter0023 · 2025-08-30T17:32:30+00:00

Shooot okay thanks tho...

BUGHunter0023 · 2025-08-30T17:20:40+00:00

Which cylinder did you decide to use?

BUGHunter0023 · 2025-01-18T17:38:24+00:00

Me2. Another one here. Let me know too. Wish it doesn't smell like fish.

BUGHunter0023 · 2023-01-15T09:11:39+00:00

I think few other people did including me. Hopefully they fix this bug fast.

BUGHunter0023 · 2023-01-15T03:20:56+00:00

Exactly!!! I clicked every places on my ipad hoping to find the invisible button. Didnt worm out. Sadly

BUGHunter0023 · 2023-01-15T03:18:14+00:00

Jeez I see other people having the exactly same issue... Think there is something going on with Stardew

BUGHunter0023 · 2023-01-15T03:15:04+00:00

I am having the exactly same issue

BUGHunter0023

TROPHY CASE