Skip to main content

TrajectoryDeadlinesScenario

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

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

A trajectory record for machine’s arm at site: a replacement requested at request_delay with a latency_target and schedule_slack, a blend deadline, the commit instant when stop (a JerkLimitedStopScenario) must begin, and a late_wait.

Notes

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

Assumptions: Inputs are routed to TrajectoryDeadlinesModel.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 TrajectoryDeadlinesModel. 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.WarehouseArmCommitmentSchedule
>>> value = case.response
>>> print(f"{value:.3g~}")
22 ms

Attributes

Name Description
blend
commit
late_wait
latency_target
machine
request_delay
response Decision-to-brake-onset delay in ms, summing tick, bus, and brake-onset delays.
result Evaluate the stated trajectory deadlines case through TrajectoryDeadlinesModel.solve; returns its typed result and quantity units.
schedule_slack
site
stop

machine

Type: Any.

Declared default: required.

site

Type: Any.

Declared default: required.

stop

Type: JerkLimitedStopScenario.

Declared default: required.

request_delay

Type: Quantity.

Declared default: required.

latency_target

Type: Quantity.

Declared default: required.

schedule_slack

Type: Quantity.

Declared default: required.

blend

Type: Quantity.

Declared default: required.

commit

Type: Quantity.

Declared default: required.

late_wait

Type: Quantity.

Declared default: required.

response

engine.scenario_types.TrajectoryDeadlinesScenario.response

Decision-to-brake-onset delay in ms, summing tick, bus, and brake-onset delays.

Decision to physical onset: one tick, one bus cycle, and the brake onset.

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

result

engine.scenario_types.TrajectoryDeadlinesScenario.result

Evaluate the stated trajectory deadlines case through TrajectoryDeadlinesModel.solve; returns its typed result and quantity units.

Calculation: mlsysim.solvers.TrajectoryDeadlinesModel.solve.

Back to top