FlexMeasures / flexmeasures / 35992145802

85%

push

github

Fix what the asset status page reports about its sensors (#2474)

* Fix what the asset status page reports about its sensors (#1718)

Three things went wrong for a sensor that another asset refers to,
such as the day-ahead price sensor in the toy tutorial:

- The most-recent-only fast track of a belief search picks the single most
  recent event in the database, and only afterwards drops beliefs that were
  formed after the moment we report the status. For a sensor with a knowledge
  horizon, that can drop the only row we fetched, which made a sensor with
  plenty of data report "no data recorded". Search again without the fast
  track when that happens, and pick the most recent event ourselves.
- Data whose knowledge time still lies ahead was held to the minimum lead time
  that only forecasters and schedulers should be held to, so prices recorded
  for tomorrow showed a red light. Such data is fresh, not stale.
- The reported relation was computed against the asset that the sensor belongs
  to, rather than against the asset whose status page is shown, so every sensor
  claimed to belong to the asset shown. The status endpoint now accepts the
  asset to report on, and the status page passes it.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* Report on sensors recorded by any source type on the status page (#1718)

The status page only looked for the default source types, so a sensor recorded
by any other type reported "no data recorded", however much data it held. The
toy tutorial hits this: `flexmeasures add beliefs` records under the type
"CLI script", so the day-ahead price sensor showed a red light with no data.

Look for the source types that actually recorded on the sensor, which the
sensor_data_source summary table answers as a plain lookup, on top of the
default types.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

* Keep one changelog entry for the status page fixes (#1718)

Co-Authored-By: Claude Opus 5 <noreply@anthropic... (continued)

19 of 22 new or added lines in 2 files covered. (86.36%)

19614 of 22831 relevant lines covered (85.91%)

0.86 hits per line