HorizonCompoundingScenario
Agents scenarios · Implementation: mlsysim/engine/scenario_definitions/agents.py.
Construct this scenario with keyword inputs. The fields below show the types and defaults declared by this class.
Independent, unchecked steps each right with step_success; success at each horizon.
Notes
Equation: Compose mlsysim.solvers.HorizonCompoundingModel.
Assumptions: The horizons count unchecked steps with the success assumptions in HorizonCompoundingModel; None removes an optional horizon.
Excludes: Task-dependent correlations or recovery behavior are absent unless represented by the chosen solver.
References
Derivation: this scenario binds its input fields to the referenced implementation contracts: mlsysim.solvers.HorizonCompoundingModel. The methods below identify any additional arithmetic.
Examples
>>> from mlsysim import Scenarios
>>> case = Scenarios.UncheckedRepairHorizon
>>> type(case.horizons).__name__
'tuple'Attributes
| Name | Description |
|---|---|
| extended_horizon | |
| horizons | Configured unchecked-step horizons with absent optional horizons removed. Equation: |
| long_horizon | |
| result | Evaluate this scenario through mlsysim.solvers.HorizonCompoundingModel.solve. |
| short_horizon | |
| step_success | |
| target_success |
step_success
Type: float.
Declared default: required.
short_horizon
Type: int.
Declared default: required.
long_horizon
Type: int.
Declared default: required.
target_success
Type: float.
Declared default: required.
extended_horizon
Type: Optional[int].
Declared default: None.
horizons
engine.scenario_types.HorizonCompoundingScenario.horizons
Configured unchecked-step horizons with absent optional horizons removed. Equation: retain non-None values from short, long, and extended horizons. Units: steps; ordering follows the inputs.
result
engine.scenario_types.HorizonCompoundingScenario.result
Evaluate this scenario through mlsysim.solvers.HorizonCompoundingModel.solve. Equation: pass the stated fields to that implementation; its contract defines the calculation and feasibility tests. Units: each returned field follows the referenced result schema; no independent equation is evaluated by this wrapper.