Skip to main content

IrreversibleLossScenario

Reliability scenarios · Implementation: mlsysim/engine/scenario_definitions/reliability.py.

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

A workload’s wrong-change risk priced with its pre-pivot check, from its agent profile.

Notes

Equation: The result property composes mlsysim.solvers.IrreversibleLossModel.solve with the stored fields and any derived properties described below.

Assumptions: Inputs use the units and validity ranges of mlsysim.solvers.IrreversibleLossModel.solve. The named scenario supplies a fixed configuration rather than observations of a new run.

Excludes: Additional runtime effects or statistical guarantees beyond the cited solver contracts; no measurement is performed by this wrapper.

References

Derivation: The result property composes mlsysim.solvers.IrreversibleLossModel.solve with the stored fields and any derived properties described below. Individual property contracts identify the exact accounting expression or reusable calculation. Registry entries supply the scenario inputs; this class does not turn them into measured outcomes.

Examples

Evaluate a named scenario using its declared inputs.

>>> from mlsysim import Scenarios
>>> scenario = Scenarios.RemediationCanaryPivotLoss
>>> round(float(scenario.attempt_cost.magnitude), 4)
20.45

Attributes

Name Description
attempt_cost USD cost per attempt copied from the remediation workload profile.
catch_step
result Return the modeled IrreversibleLoss result from
workload

workload

Type: Any.

Declared default: required.

catch_step

Type: float.

Declared default: required.

attempt_cost

engine.scenario_types.IrreversibleLossScenario.attempt_cost

USD cost per attempt copied from the remediation workload profile.

Equation: workload.attempt_cost.

result

engine.scenario_types.IrreversibleLossScenario.result

Return the modeled IrreversibleLoss result from mlsysim.solvers.IrreversibleLossModel.solve.

Equation: the scenario supplies its named fields to that solver. Returned quantity units, validity conditions, and omissions follow its calculation contract; this property adds no empirical calibration.

Back to top