v12

Changes in this version:

• minor changes to the backend
• reorganisation of exported vuoro lists
• removal of sequence information (this data is no longer available - see here).
• minor fixes and changes to the readme due to the above

Full Changelog: v11...v12

v11

Changes to vuoro collection and display, along with minor cosmetic changes to the main display and a completely rewritten Readme for ease of understanding.

Full Changelog: v10...v11

v10

Version 10: The Big Fix Update

Here's what's changed (in order of importance):

• Vuoros (internal train service numbers) are now scraped from the MQTT data (I hadn't realised this was possible and I don't think it's intentional). This also makes the program significantly more immune to uudelleenvuorotus (where train numbers are swapped during the day because of disruption) and random impromptu timetable changes.
• Alerts and disruptions currently valid on the metro are displayed at the bottom of the table.
• For M100s and M200s, the leading unit is shown preceded by a caret (^).
• Special markers have been added to certain units to show special features of certain trains (e.g. ad wraps).
• The algorithm for connecting M100s and M200s which are running in multiple has been made more robust to completely eliminate false positives.
• The file structure has changed significantly for ease of use and the readme has also been completely rewritten to aid understanding and ease of use.
• The core code has been cleaned up significantly (especially the first portion) and comments have been added to ease readability and maintainability.
• M2A handling has been updated to deal with the new timetables (7.1.2025-4.5.2025).
• An automatic facility has been provided to tell the user if all traffic has been stopped. This relies on every train being in a platform.
• Wrong-direction running (yhden raiteen ajo tai väärän raiteen ajo) is now reflected in the program, albeit untested (because this requires significant real-world disruption to test). It's not perfect, and there are no ETAs, but it works (for now).
• Extra pieces of vesitigial (commented out) code have been included (lines 77 & 193-196) to allow one to crudely change the destinations of trains, e.g. during very significant disruption when a section of line is closed.
• Trains in the turning section of KPG (Kampin kääntöraide) will now show up. Trains in the holding tracks, however, will not.
• Various other small things have been fixed and umpteen bugs have been...erm...debugged, making the code more robust and featureful.
• The code can now run reliably for well over half an hour without any issues.

Full Changelog: v8.1...v10

v8.1

I've fixed M2A handling on Friday-Sunday, which was completely broken because I counted from 0, not 1!

I've also added some new coords for probable use in a future release.

Full Changelog: v8.0.1...v8.1

v8.0.1

Minor changes to remove a debug thing I left in to help me code M2A handling :)

No change to the core code.

What's Changed

• Removed vestigial debug print statement by @IsoPorksu in #1

New Contributors

• @IsoPorksu made their first contribution in #1

Full Changelog: v8...v8.0.1

v8

TrueTrack is now complete!

This release essentially does what it says on the tin - the TrueTrack project is now complete and ready for full use!

Smoothly incrementing ETAs might come along at a later date, but otherwise, all features work fine. It is, however, not reccomended to run the program for more than 1000 seconds without restarting it, especially during the ends of the peaks and the end of services.

Known issues:

• Trains are never removed from the list; if a train is removed from service, it will remian on the list until the program is restarted.
• If a train is turned short of its destination (e.g. at Ruoholahti or Itäkeskus) due to short-term disruption, this will not be reflected in the program because there is no data available for it (and there most likely never will be).
• Wrong-direction running (yhden raiteen ajo tai väärän raiteen ajo) is not reflected in the program due to the amount of work required to implement this, though it may be implemented in a limited capacity at a later date.
• In very rare cases during midweek peaks (i.e. when the service frequency is ~24tph), three or (occasionally) four M100/M200 sets may be listed as being in the same position, for reasons currently unknown; this causes the M1 and M2 counters to frequently change by 0.5.

Full Changelog: release...v8

v4

TrueTrack is now ready for use. Minor changes to the handling of MM-KIL services will be coming along shortly and changes to ETA estimations will drop in the next few days.

Full Changelog: https://github.com/IsoPorksu/TrueTrack/commits/release