Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | Forget it, and use the old preset tables for track registration. Just adapt ↵ | orwell | 2023-10-15 |
| | | | | it to the new definition. | ||
* | Begin major rework of track registration system | orwell96 | 2023-09-04 |
| | |||
* | Add lines scheduler for reliable railway-time scheduling(which is also safer ↵ | orwell96 | 2019-08-26 |
| | | | | than the atlatc scheduler) and document new atlatc functions | ||
* | Railway Time: atlatc interface, improve util functions | orwell96 | 2019-06-19 |
| | |||
* | Railway Time: Basic time counter and utility functions | orwell96 | 2019-06-19 |
| | |||
* | Basic functions of "stop rail", missing ARS rules and signal. | orwell96 | 2019-01-24 |
| | | | | For signal, need to think of a callback system for signals and moving atlatc queue to core? | ||
* | Point speed restriction rails | orwell96 | 2019-01-24 |
| | |||
* | Added on_train_approach callback, non-permanent external LZB brakepoints and ↵ | orwell96 | 2018-11-29 |
basis for "stop rails" Stop rails ATM use the aforementioned things to add a pointwise "2" speed restriction. Seems to work. |