Feat/offtick soc projection

documentation/changelog.rst

@@ -12,8 +12,8 @@ v1.0.0 | July XX, 2026
 
 New features
 -------------
+* Floor off-clock API datetimes to a non-instantaneous sensor's resolution by default when ingesting sensor data, uploading sensor data, and handling scheduler flex-model timed events; configurable with the ``floor_datetimes_to_resolution`` sensor attribute [see `PR #2146 <https://www.github.com/FlexMeasures/flexmeasures/pull/2146>`_ and `PR #2194 <https://www.github.com/FlexMeasures/flexmeasures/pull/2194>`_]
 * In the UI, asset and sensor lists can be filtered by ID prefix through API-backed search fields [see `PR #2231 <https://www.github.com/FlexMeasures/flexmeasures/pull/2231>`_]
-* Floor off-clock API datetimes to a non-instantaneous sensor's resolution by default when ingesting sensor data, uploading sensor data, and handling scheduler flex-model timed events; configurable with the ``floor_datetimes_to_resolution`` sensor attribute [see `PR #2146 <https://www.github.com/FlexMeasures/flexmeasures/pull/2146>`_]
 * Sensor references in flex-model and flex-context support various ways of filtering by source [see `PR #2209 <https://www.github.com/FlexMeasures/flexmeasures/pull/2209>`_]
 * Let storage scheduling infer missing ``power-capacity`` from directional device capacities before falling back to site capacity, and default the missing opposite capacity to zero when only a non-zero ``consumption-capacity`` or ``production-capacity`` is configured [see `PR #2222 <https://www.github.com/FlexMeasures/flexmeasures/pull/2222>`_]
 * CLI support for adding/editing account attributes [see `PR #2242 <https://www.github.com/FlexMeasures/flexmeasures/pull/2242>`_]

documentation/concepts/data-model.rst

@@ -100,6 +100,26 @@ Each belief links to a sensor and a data source. Here are two examples:
 See also :ref:`one_or_multiple_sensors` for guidance on when such beliefs are best recorded on one shared sensor and when separate sensors are preferable.
 
 
+.. _projecting_scheduling_constraints:
+
+Projecting scheduling constraints to a fixed resolution
+^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+
+Schedulers operate on a fixed scheduling resolution, such as 15 minutes.
+This means the optimization problem can enforce state-of-charge constraints only on the scheduling ticks implied by that resolution.
+When a storage flex-model contains point-like ``soc-targets``, ``soc-minima`` or ``soc-maxima`` between two scheduling ticks, FlexMeasures projects those constraints onto the surrounding ticks instead of simply flooring them.
+
+For an off-tick ``soc-target``, the target value is moved to the next scheduling tick as an exact target.
+The previous tick receives lower and upper bounds that reflect how much the asset could still charge or discharge between the previous tick and the original target time.
+For off-tick ``soc-minima``, both surrounding ticks receive lower bounds that preserve whether the requested minimum can still be reached.
+For off-tick ``soc-maxima``, both surrounding ticks receive upper bounds with the same reachability logic.
+
+The projection uses the ``consumption-capacity`` and ``production-capacity`` active at the relevant ticks.
+If multiple projected lower bounds land on the same tick, the highest lower bound is kept.
+If multiple projected upper bounds land on the same tick, the lowest upper bound is kept.
+Because projection can introduce additional bounds and more complex combinations can become infeasible, FlexMeasures enables ``relax-soc-constraints`` automatically when off-tick SoC constraints are submitted.
+
+
 .. _signs_of_power_beliefs:
 
 About signs of power & energy values

documentation/features/scheduling.rst

@@ -253,6 +253,8 @@ For more details on the possible formats for field values, see :ref:`variable_qu
 
 .. [#minimum_overlap] In case this field defines partially overlapping time periods, the minimum value is selected. See :ref:`variable_quantities`.
 
+.. [#projecting_scheduling_constraints] Off-tick ``soc-targets``, ``soc-minima`` and ``soc-maxima`` are projected to the surrounding scheduling ticks. See :ref:`projecting_scheduling_constraints`.
+
 For more details on the possible formats for field values, see :ref:`variable_quantities`.
 
 Usually, not the whole flexibility model is needed.

flexmeasures/api/v3_0/tests/test_sensors_api_freshdb.py

@@ -246,7 +246,7 @@ def test_upload_sensor_data_with_unit_conversion_success(
             len(beliefs) == expected_num_beliefs
         ), f"Fetched {len(beliefs)} beliefs from the database, expecting {expected_num_beliefs}."
 
-        assert [b.event_value for b in beliefs] == expected_event_values
+        assert [b.event_value for b in beliefs] == pytest.approx(expected_event_values)
 
 
 @pytest.mark.parametrize(