Skip to content

Feat/schedule resolution #1857

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
Flix6x wants to merge 22 commits into
base: main
Choose a base branch
from
Open

Feat/schedule resolution #1857

Flix6x wants to merge 22 commits into from

Conversation

@Flix6x
Copy link
Contributor

@Flix6x Flix6x commented Dec 9, 2025 •
edited
Loading

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.

...

Flix6x added 10 commits December 9, 2025 11:05
@Flix6x
feat: add API support for resolution field
ec49acf 
Signed-off-by: F.N. Claessen <[email protected]>
@Flix6x
feat: test whether new field makes it into the job kwargs
8928bea 
Signed-off-by: F.N. Claessen <[email protected]>
@Flix6x
feat: pass on the resolution to make_schedule
9c1d6de 
Signed-off-by: F.N. Claessen <[email protected]>
@Flix6x
fix: resample from scheduling resolution to sensor resolution
a8a3bb1 
Signed-off-by: F.N. Claessen <[email protected]>
@Flix6x
fix: convert storage efficiency from sensor resolution to scheduling …
b716500 
…resolution

Signed-off-by: F.N. Claessen <[email protected]>
@Flix6x
feat: only allow resolutions that are a multiple of the sensor resolu…
4536e1c 
…tion

Signed-off-by: F.N. Claessen <[email protected]>
@Flix6x
feat: cover new feature in a test
869f685 
Signed-off-by: F.N. Claessen <[email protected]>
@Flix6x
fix: optional arguments
9b181c8 
Signed-off-by: F.N. Claessen <[email protected]>
@Flix6x
fix: only use coarser resolution for tests where the targets are stil…
e44adcb 
…l on the tick

Signed-off-by: F.N. Claessen <[email protected]>
@Flix6x
fix: don't resample the instantaneous soc sensor data
c06b76e 
Signed-off-by: F.N. Claessen <[email protected]>
@Flix6x Flix6x added this to the 0.31.0 milestone Dec 9, 2025
@Flix6x Flix6x self-assigned this Dec 9, 2025
@Flix6x Flix6x added enhancement New feature or request API Scheduling labels Dec 9, 2025
@read-the-docs-community
Copy link

read-the-docs-community bot commented Dec 9, 2025 •
edited
Loading

Documentation build overview

📚 flexmeasures | 🛠️ Build #30897915 | 📁 Comparing 3225d0b against latest (62b4f20)


🔍 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

@Flix6x Flix6x requested a review from nhoening January 6, 2026 00:15
@Flix6x
fix: Python3.9 compatibility
e252d27 
Signed-off-by: F.N. Claessen <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@nhoening nhoening Awaiting requested review from nhoening

At least 1 approving review is required to merge this pull request.

Assignees

@Flix6x Flix6x

Labels

API CLI enhancement New feature or request Scheduling

Projects

None yet

Milestone

0.31.0

Development

Successfully merging this pull request may close these issues.

Scheduling with custom resolution

2 participants

@Flix6x