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

design-doc: rename (shorten) 'on_stop_signal' flag for timetable #192

Merged
merged 1 commit into from
Apr 26, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions content/docs/reference/design-docs/timetable/index.en.md
Original file line number Diff line number Diff line change
Expand Up @@ -139,12 +139,12 @@ constraint_distribution: MARECO # or LINEAR
# times are defined as time elapsed since start. Even if the attribute is omitted,
# a scheduled point at the starting point is infered to have departure=start_time
# the "locked" flag is ignored by the backend.
# To force a stop signal, you can use the "arrival_on_stop_signal" flag.
# To force stop-signal on stop's arrival, you can use the "on_stop_signal" flag.
schedule:
- {at: a, stop_for: PT5M, locked: true} # infered arrival to be equal to start_time
- {at: b, arrival: PT10M, stop_for: PT5M}
- {at: c, stop_for: PT5M}
- {at: d, arrival: PT50M, locked: true, arrival_on_stop_signal: true}
- {at: d, arrival: PT50M, locked: true, on_stop_signal: true}

margins:
# This example encodes the following margins:
Expand Down
Loading