PueRetrofitScenario
Sustainability scenarios · Implementation: mlsysim/engine/scenario_definitions/sustainability.py.
Construct this scenario with keyword inputs. The fields below show the types and defaults declared by this class.
A fixed IT load moved from pue_before to pue_after for period at an electricity price.
Notes
Equation: The result property composes mlsysim.solvers.PueRetrofitModel.solve with the stored fields and any derived properties described below.
Assumptions: Inputs use the units and validity ranges of mlsysim.solvers.PueRetrofitModel.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.PueRetrofitModel.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.PueRetrofit2MW
>>> round(float(scenario.result.facility_power_before.magnitude), 4)
3.16Attributes
| Name | Description |
|---|---|
| electricity_price | |
| it_power | |
| period | |
| pue_after | |
| pue_before | |
| result | Return the modeled PueRetrofit result from mlsysim.solvers.PueRetrofitModel.solve. |
it_power
Type: Quantity.
Declared default: required.
pue_before
Type: float.
Declared default: required.
pue_after
Type: float.
Declared default: required.
period
Type: Quantity.
Declared default: required.
electricity_price
Type: Quantity.
Declared default: required.
result
engine.scenario_types.PueRetrofitScenario.result
Return the modeled PueRetrofit result from mlsysim.solvers.PueRetrofitModel.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.