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.

Sign up for GitHub

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

Jump to bottom

Enhanced signal visibility distance #4923

Closed
flomonster opened this issue Aug 29, 2023 · 0 comments · Fixed by #4924
Closed

Enhanced signal visibility distance #4923

flomonster opened this issue Aug 29, 2023 · 0 comments · Fixed by #4924
Assignees
@Khoyo
Labels
area:core Work on Core Service component:simulation

Comments

@flomonster
Copy link
Contributor

flomonster commented Aug 29, 2023 •
edited
Loading

What is this feature about?

Most of our infra have a signal with a visibility distance set to 400m. It's a great default value but we should take into account the distance between signals. For example, if you have a line with signals close to each other we shouldn't take into account a signal further than the next one (as below).

image

In other words, the visibility distance cannot take on a value greater than the distance between the signals.

Why is this feature valuable?

More precise spacing resource generation and better GET.

Anything else people should know?

No response
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Khoyo Khoyo

Labels
area:core Work on Core Service component:simulation
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

core: trains cannot see a signal before passing the previous one OpenRailAssociation/osrd
2 participants
@Khoyo @flomonster