aboutsummaryrefslogtreecommitdiff
path: root/lib/Extrapolation.hs (unfollow)
Commit message (Collapse)AuthorFilesLines
2024-05-15Server.Ingest: new handling of unassigned trackersstuebinm1-12/+12
now takes all potential stops along each trip into account when guessing tickets; also checks if a ticket is still likely in case the tracker switched its direction. This should solve many cases where a tracker is accidentally turned off or falls asleep halfway before the last station of one trip, then wakes up in the middle of the next.
2024-05-02restructure: get the tracker to work againstuebinm1-4/+5
This should hopefully be the final (major) part of the restructuring: a tracker no longer has to know which trip it is on (and indeed it has no idea for now), instead the server keeps state about which trips are currently running and will insert incoming pings in a hopefully reasonable manner, based on their geoposition & time. There's lots of associated TODO items here (especially there should be manual overrides for all this logic in the web ui), but that's work for a future me. (incidentally, this also adds support for sending all log messages out via ntfy-sh)
2024-04-24restructure: save a ticket's stop in the databasestuebinm1-60/+83
now mostly independent of the gtfs, but still no live-reloading of it.
2024-04-20restructure: have "tickets" independent of gtfsstuebinm1-12/+10
this is mostly meant to guard against the gtfs changing under tracktrain, and not yet complete (e.g. a ticket does not yet save its expected stops, which it probably should).
2024-04-17general housekeepingstuebinm1-9/+5
jumps to GHC2021 as default language, adds in some fields, moves the old org mode glossary to markdown, etc.
2022-09-14remove some extrapolation bugsstuebinm1-52/+57
2022-09-10gtfs realtime: add tripUpdate feedstuebinm1-12/+5
2022-09-09fix the close-to-a-station bugstuebinm1-22/+31
(previously tracktrain could end up in a situation where the next and last station weren't actually adjacent stops, which messed up the prediction)
2022-09-02reasonable delay forecastsstuebinm1-36/+55
2022-08-31guess at future delays (horrible, incorrect, and unfinished)stuebinm1-27/+42
2022-08-28some config thingyesodstuebinm1-3/+3
works kinda well, but doesn't complain about unknown config values in json, which is kinda hmpf tbh
2022-08-28this does way too much tbh (also functioning delays)stuebinm1-0/+97
most of it deals with timezones, and all the weird implications that has