• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

FlexMeasures / flexmeasures / 37464422189
87%

Build:
DEFAULT BRANCH: main
Ran 06 Oct 2026 12:45PM UTC
Jobs 1
Files 190
Run time 1min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

06 Oct 2026 12:35PM UTC coverage: 86.412% (+0.08%) from 86.335%
37464422189

push

github

web-flow
Record a forecaster's input qualifiers in its config, named "auto" (#2627)

* data/schemas/forecasting: let a config name the sensor being forecast as "auto"

A forecaster's config describes the sensors it reads, but had no way to describe the one it forecasts, which the forecast parameters name. Writing "auto" in place of a sensor ID names that sensor without tying the config to one target, and qualifying it says which of its sources to train on and how to clean its readings.

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

* data/models/forecasting: read the sensor being forecast as its config entry describes it

The model learns from that sensor, as its labels and as its own lags, so a config entry naming it says how to read it rather than handing it to the model a second time: such an entry is taken out of the regressor lists and describes the target instead. The config keeps naming "auto", because that is what the data source records; running resolves it against the sensor the forecast names.

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

* data/models/forecasting: move target qualifiers out of the run parameters into the config

The sensor being forecast could briefly be given source filters and cleaning bounds in the forecast parameters, which a forecaster does not record on its data source, so neither reached the data-generator attributes and a forecaster trained on cleaned data was attributed to the same source as one trained on raw data.

A payload that still carries them keeps working: they move to a config entry naming "auto", with a warning, and the parameters name the sensor alone.

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

* docs: say that a forecaster's config describes the sensor it forecasts too

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

116 of 117 new or added lines in 6 files covered. (99.15%)

2 existing lines in 1 file now uncovered.

21114 of 24434 relevant lines covered (86.41%)

0.86 hits per line

Uncovered Changes

Lines Coverage ∆ File
1
97.58
-0.22% flexmeasures/data/models/forecasting/pipelines/train_predict.py

Coverage Regressions

Lines Coverage ∆ File
2
94.0
-0.15% flexmeasures/data/services/automations.py
Jobs
ID Job ID Ran Files Coverage
1 37464422189.1 06 Oct 2026 12:45PM UTC 190
86.41
GitHub Action Run
Source Files on build 37464422189
  • Tree
  • List 190
  • Changed 4
  • Source Changed 4
  • Coverage Changed 4
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #37464422189
  • 8bff96dc on github
  • Prev Build on main (#37447223201)
  • Next Build on main (#37499108173)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE TRIAL · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc