Feat/schedule resolution

[Flix6x]

Description

• Support setting a resolution when triggering a schedule via the API
• A similar --resolution option in the CLI for flexmeasures add schedule
• Fix conversion of the storage efficiency per device (which is defined relative to the resolution of each device's power sensor) to the scheduling resolution (which defaulted to the smallest non-zero resolution amongst the devices)
• Fix resampling the scheduling results to the resolution of the power sensor of each device
• Added changelog item in documentation/changelog.rst

Look & Feel

...

How to test

• Added coverage for sensor API in test_trigger_and_get_schedule
• Added coverage for asset API in test_asset_trigger_and_get_schedule

Further Improvements

• Needs to be followed up with a flexmeasures-client PR

Related Items

Closes #1856.

...

[read-the-docs-community]

Documentation build overview

📚 flexmeasures | 🛠️ Build #31254451 | 📁 Comparing a028b6c against latest (36400dd)

🔍 Preview build

Show files changed (4 files in total): 📝 4 modified | ➕ 0 added | ➖ 0 deleted

File	Status
changelog.html	📝 modified
_autosummary/flexmeasures.api.v3_0.assets.html	📝 modified
_autosummary/flexmeasures.api.v3_0.sensors.html	📝 modified
api/v3_0.html	📝 modified

[nhoening]

I tested this in the CLI via the first tutorial and ran into a problem.

I used docker compose and ran the script, only with --resolution PT2H added to the flexmeasures add schedule command.

The function ensure_prices_are_not_empty() complained (see below), I suspect because get_continuous_series_sensor_or_quantity() cannot get the data if the resolution passed to it doesn't match the sensor resolution? I did not pursue that until the end (TimedBelied.search()).

 File "/usr/local/lib/python3.12/dist-packages/flexmeasures/cli/data_add.py", line 1444, in add_schedule
    success = make_schedule(
              ^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/dist-packages/flexmeasures/data/services/scheduling.py", line 584, in make_schedule
    consumption_schedule: SchedulerOutputType = scheduler.compute()
                                                ^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/dist-packages/flexmeasures/data/models/planning/storage.py", line 1318, in compute
    ) = self._prepare(skip_validation=skip_validation)
        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/dist-packages/flexmeasures/data/models/planning/storage.py", line 187, in _prepare
    ensure_prices_are_not_empty(up_deviation_prices, consumption_price)
  File "/usr/local/lib/python3.12/dist-packages/flexmeasures/data/models/planning/utils.py", line 96, in ensure_prices_are_not_empty
    raise UnknownPricesException(error_message)
flexmeasures.data.models.planning.exceptions.UnknownPricesException: Prices unknown for planning window. (sensor 1)

[Flix6x]

@nhoening I fixed the issue in timely-beliefs; the tutorial should now work with a 2-hour resolution. Please verify.