We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Actually, I have some doubts as to whether get_intersections is the function we need. There's a slight difference between the train schedule projection and the work schedule projection: A train schedule path is linear, a work schedule track ranges are not A PathProjection required unique tranck sections, which might not be the case for work schedule track ranges I think we could adapt the get_intersections function to make it work in the general case (work schedule). This could be done in a later PR.
Actually, I have some doubts as to whether get_intersections is the function we need.
get_intersections
There's a slight difference between the train schedule projection and the work schedule projection:
I think we could adapt the get_intersections function to make it work in the general case (work schedule). This could be done in a later PR.
Originally posted by @flomonster in #8794 (comment)
The text was updated successfully, but these errors were encountered:
anisometropie
No branches or pull requests
Originally posted by @flomonster in #8794 (comment)
The text was updated successfully, but these errors were encountered: