FlexMeasures / flexmeasures / 37856750854

87%

main: 87%

Pull #2693

github

Derive an instantaneous target's resolution in the forecaster, over its training window and with its source filters

The resolution to forecast an instantaneous sensor at, when none is given, was derived in the parameters schema,
from the sensor's readings in the 30 days before the predictions start.
It is now derived by the forecaster before any cycle is run or queued, next to the training period,
from the readings the model trains on: over the configured training window, before the prior, and with the source filters of the forecaster's "auto" entry
(without filters, leaving out forecasts, as the training data does).
The order stays: the sensor's frequency attribute, the most common duration between those readings snapped to whole minutes, or else one hour.

A default start is now left unfloored by the schema for such a sensor, and aligned to the derived resolution by the forecaster,
moving an end that was derived from it along.
The check that max-forecast-horizon and forecast-frequency are multiples of a derived resolution moves along too, and still says where the value came from;
an explicit resolution, or a sensor's own, is still checked by the schema.
The API trigger still answers 422, and the CLI still reports the error, as both run this before anything is queued.
The interpolation attributes of the instantaneous sensors involved are also checked then.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Signed-off-by: F.N. Claessen <claessen@seita.nl>

262 of 267 new or added lines in 7 files covered. (98.13%)

21691 of 25006 relevant lines covered (86.74%)

0.87 hits per line