From 6bf06f209952d3dd5dd773297873660ae8296e2f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Pierre-Etienne=20Bougu=C3=A9?= Date: Wed, 25 Sep 2024 12:17:11 +0200 Subject: [PATCH] doc: precise short slip distance use in train-schedule MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit after reviews on https://github.com/OpenRailAssociation/osrd/pull/8983 Signed-off-by: Pierre-Etienne Bougué --- content/docs/reference/design-docs/timetable/index.en.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/content/docs/reference/design-docs/timetable/index.en.md b/content/docs/reference/design-docs/timetable/index.en.md index 28ef60690..e04d8de8a 100644 --- a/content/docs/reference/design-docs/timetable/index.en.md +++ b/content/docs/reference/design-docs/timetable/index.en.md @@ -149,6 +149,8 @@ constraint_distribution: MARECO # or LINEAR # speed on approach as well as short slip distance speed. # This is used for cases were a movable element is placed shortly after the signal # and going beyond the signal would cause major problems. +# This is used automatically for any stop before a buffer-stop. +# This is also the default use for STDCM stops, as it is the most restrictive. schedule: - {at: a, stop_for: PT5M, locked: true} # infered arrival to be equal to start_time - {at: b, arrival: PT10M, stop_for: PT5M}