Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Diversionary calling points can get into the aggregated data. #2

Open
grundleborg opened this issue Sep 30, 2015 · 0 comments
Open

Comments

@grundleborg
Copy link
Member

When a train is diverted on the first day the aggregator sees it, any diversionary calling points end up permanently in it's schedule in the aggregated data. This is bad.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant