Skip to main content

RailHoldUpScenario

Robotics scenarios · Implementation: mlsysim/engine/scenario_definitions/robotics/diagnostics.py.

Construct this scenario with keyword inputs. The fields below show the types and defaults declared by this class.

site.machine’s backed permission rail, its feed lost during the longest admitted stop.

The longest stop starts at the speed ceiling of stop (a finished StoppingBudgetScenario); the flag path is one tick, one bus cycle, and the brake onset of site; engagement and hold-up are the machine’s.

Notes

Equation: Composition of mlsysim.solvers.RailHoldUpModel.solve.

Assumptions: Inputs are routed to RailHoldUpModel.solve; their documented regimes and units apply to this configuration.

Excludes: Additional mechanisms beyond the linked solver contracts; the scenario does not collect measurements.

References

Derivation: This scenario binds named inputs to RailHoldUpModel. The linked solver contracts own equations, sources, and result-unit definitions.

Examples

Evaluate the named configuration and display a modeled result.

>>> from mlsysim import Scenarios
>>> case = Scenarios.WarehousePermissionRailHoldUp
>>> value = case.result.flag_to_set
>>> print(f"{value:.3g~}")
1.31e+03 ms

Attributes

Name Description
flag_path Fault-to-brake-onset path in ms, tick plus bus plus brake onset.
result Evaluate the stated rail hold up case through RailHoldUpModel.solve; returns its typed result and quantity units.
site
stop

site

Type: Any.

Declared default: required.

stop

Type: StoppingBudgetScenario.

Declared default: required.

flag_path

engine.scenario_types.RailHoldUpScenario.flag_path

Fault-to-brake-onset path in ms, tick plus bus plus brake onset.

Equation: (s.t_tick + s.t_bus + s.t_brake_onset).to('ms').

result

engine.scenario_types.RailHoldUpScenario.result

Evaluate the stated rail hold up case through RailHoldUpModel.solve; returns its typed result and quantity units.

Calculation: mlsysim.solvers.RailHoldUpModel.solve.

Back to top