Feat/offtick soc projection

[BelhsanHmida]

Description

• Project off-tick storage SoC constraints onto the scheduling ticks using charge/discharge capacity, instead of blindly flooring timed soc-targets, soc-minima, and soc-maxima.
• [x]Preserve original SoC event times during storage flex-model schema deserialization so scheduler logic can interpret the user’s intent.
• Automatically enable relax-soc-constraints when off-tick SoC constraints are submitted, so generated/adjusted constraints can be softened safely.
• Added tests for off-tick SoC target projection and automatic SoC constraint relaxation.
• add changelog entry.

How to test

pytest flexmeasures/api/v3_0/tests/test_sensor_schedules.py flexmeasures/data/schemas/tests/test_scheduling.py flexmeasures/data/models/planning/tests/test_storage.py -q

Manual test:

• Trigger a storage schedule with a 15-minute resolution and an off-tick soc-target, e.g. 17:12.
• Use 0.04 MW charging capacity and target 1 MWh.
• Verify the scheduler does not floor the target to 17:00, but projects it onto the scheduling ticks as an adjusted previous-tick bound and a next-tick target.
• Verify off-tick SoC constraints enable relax-soc-constraints.

Projection policy

The scheduler can enforce SoC constraints only on its scheduling ticks. For point-like off-tick SoC events:

• soc-targets are projected to an exact target on the next scheduling tick, with capacity-adjusted lower and upper bounds on the previous tick.
• soc-minima are projected as lower bounds on the surrounding ticks, adjusted by reachable charge/discharge capacity.
• soc-maxima are projected as upper bounds on the surrounding ticks, adjusted by reachable charge/discharge capacity.
• If multiple projected lower bounds land on the same tick, the stricter lower bound is kept.
• If multiple projected upper bounds land on the same tick, the stricter upper bound is kept.

Related Items

Follow-up to PR #2146 review discussion around off-tick storage SoC constraints.

Sign-off

• I agree to license my contributions under the project’s license.
• I signed off my commits.

[Copilot]

Pull request overview

This PR updates storage scheduling to preserve user-provided (off-tick) SoC constraint timings during flex-model deserialization, and then projects those constraints onto the scheduler’s time grid using charge/discharge capacity so they remain enforceable. It also auto-enables SoC constraint relaxation when off-tick constraints are present, and adds tests for off-tick target projection + auto-relax behavior.

Changes:

• Stop flooring SoC event datetimes during storage flex-model schema deserialization (preserve original event times).
• Normalize/project off-tick SoC constraints onto the scheduling grid inside the storage scheduler using capacity-derived bounds.
• Auto-enable relax-soc-constraints when off-tick SoC constraints are detected; add regression tests for target projection and auto-relax.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.

File	Description
flexmeasures/data/schemas/scheduling/storage.py	Removes schema-level datetime flooring for soc-targets/soc-minima/soc-maxima so original timings are preserved.
flexmeasures/data/models/planning/storage.py	Adds detection of off-tick SoC constraints, enables relaxation automatically, and normalizes/project off-tick constraints onto the scheduling grid during _prepare.
flexmeasures/data/models/planning/tests/test_storage.py	Adds tests for off-tick SoC target projection and automatic enabling of SoC constraint relaxation.

Comments suppressed due to low confidence (1)

flexmeasures/data/models/planning/storage.py:1125

• For multi-device scheduling (self.flex_model is a list), off-tick SoC events are checked against self.resolution only. When resolution is omitted, _prepare later derives it (or falls back) based on the sensors’ event resolutions, but this early check returns False with resolution=None, so relax-soc-constraints won’t be auto-enabled even though off-tick events will be projected later. Consider deriving a resolution here in the same way _prepare does (minimum non-zero sensor resolution, with default fallback) before calling flex_model_has_off_tick_soc_constraints.

        if isinstance(self.flex_model, list):
            return any(
                flex_model_has_off_tick_soc_constraints(
                    flex_model, resolution=self.resolution
                )
                for flex_model in self.flex_model
            )

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[Flix6x]

Thanks for this. I still need to check the tests and the actual projection policy, but I'd like to hold that off until it's more documented.