feat: Split flex-context settings by commodity for dynamic capacity scheduling

[Ahmad-Wahid]

Description

This PR updates the dynamic consumption capacity scheduling test to use split, commodity-specific flex-context settings for electricity and gas. It adds dynamic electricity and gas price data so the scheduler can prefer the electric heater when electricity is cheaper and the gas boiler when gas is cheaper, while ensuring that the dynamic electricity site consumption capacity is only applied to electricity devices and does not incorrectly constrain gas devices.

• Added changelog item in documentation/changelog.rst

Look & Feel

flex_context = {
        "commodities": [
            {
                "commodity": "electricity",
                "consumption-price": {
                    "sensor": consumption_price.id,
                },
                "production-price": {
                    "sensor": consumption_price.id,
                },
                "site-power-capacity": "1900 kW",
                "site-consumption-capacity": {
                    "sensor": dynamic_consumption_capacity.id,
                },
                "site-production-capacity": "100 kW",
                "site-consumption-breach-price": "100000 EUR/kW",
                "site-production-breach-price": "100000 EUR/kW",
            },
            {
                "commodity": "gas",
                "consumption-price": {
                    "sensor": gas_price.id,
                },
                "production-price": {
                    "sensor": gas_price.id,
                },
                # No electricity dynamic capacity here.
                "site-consumption-capacity": "100000 kW",
            },
        ],
        "relax-constraints": True,
        "inflexible-device-sensors": [building_raw_power.id],
    }

...

How to test

pytest -k test_simulation_with_dynamic_consumption_capacity

...

Further Improvements

...

Related Items

...

---

Sign-off

• I agree to contribute to the project under Apache 2 License.
• To the best of my knowledge, the proposed patch is not based on code under GPL or other license that is incompatible with FlexMeasures

[Flix6x]

Quick review. Also please triage the failing test suite.

[Flix6x]

Let's shorten this, by looping over all flex-context fields except the ones you wish to exclude. The commitments and inflexible-device-sensors, for instance, are also about electricity devices, and they are missed right now.

I think the only ones you want to exclude are the gas ones and the constraint relaxations.

[Flix6x]

I want to let go of this constraint. I suggest moving this list to

metadata={
    "description": "<please suggest something>",
    "examples": ["electricity", "gas"],
}

[Ahmad-Wahid]

Sorry, I didn't understant this comment.

[Flix6x]

I meant that:

1. We should not limit commodity to just those two options. I want to let users freely define commodities.
2. We can still use the ["electricity", "gas"] list, but then use it as an example only (not a restriction). Examples can be defined using the metadata argument of fields.Str (together with a field description).