ChunkReplacementScenario
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.
Replacing machine’s admitted chunk at site: capture-to-admission latency against the renewal period and the chunk lease, with an interference_tail on the inference pass.
Notes
Equation: Composition of mlsysim.solvers.ChunkReplacementModel.solve.
Assumptions: Inputs are routed to ChunkReplacementModel.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 ChunkReplacementModel. 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.WarehouseArmChunkReplacement
>>> value = case.renewal_period
>>> print(f"{value:.3g~}")
50 msAttributes
| Name | Description |
|---|---|
| interference_tail | |
| machine | |
| renewal_period | Chunk renewal interval in ms, the reciprocal of the machine’s chunk rate. |
| result | Evaluate the stated chunk replacement case through ChunkReplacementModel.solve; returns its typed result and quantity units. |
| site |
machine
Type: Any.
Declared default: required.
site
Type: Any.
Declared default: required.
interference_tail
Type: Quantity.
Declared default: required.
renewal_period
engine.scenario_types.ChunkReplacementScenario.renewal_period
Chunk renewal interval in ms, the reciprocal of the machine’s chunk rate.
Equation: (1 / machine.chunk_rate).to('ms').
result
engine.scenario_types.ChunkReplacementScenario.result
Evaluate the stated chunk replacement case through ChunkReplacementModel.solve; returns its typed result and quantity units.
Calculation: mlsysim.solvers.ChunkReplacementModel.solve.