-
Notifications
You must be signed in to change notification settings - Fork 4
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
Question about orientation vs direction #9
Comments
Hi @timvanoostrom, good question. You are right, the BiDiB protocol for MSG_CS_DRIVE messages says that it should be When we were developing an automatic train driving algorithm, the notion of a train being "forward" or "reverse" seemed ambiguous because it depends on the polarity of the track rails and on the orientation of the train. For example, if the train is "forward", would the train drive forwards to the left or to the right? This was the rationale behind using However, now that we've had more experience with our model railway (track plan), we can define |
Or to avoid ambiguity (a bit), |
Forward, backward, and reverse aren't always suitable when a train has gone through a reversing loop. In the image below, the train begins in the Left and right aren't always suitable when people do not realise that a collection of tracks are on opposite sides of a loop: I don't know whether there is a suitable solution to this problem 😄 |
Indeed. |
Hello, I was looking at this commit d2ed8ca#diff-50d858e0985ecc7f60418aaf0cc5ab587f42c2570a884095a9e8ccacd0f6545c and was wondering, what is the reason this was renamed? A loco is more likely to be recognized and addressed by it's driving direction than it's left/right orientation.
The text was updated successfully, but these errors were encountered: