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

FlexMeasures / flexmeasures / 30712612355
83%

Build:
DEFAULT BRANCH: main
Ran 01 Aug 2026 06:43PM UTC
Jobs 1
Files 172
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

01 Aug 2026 06:28PM UTC coverage: 83.298% (+0.03%) from 83.271%
30712612355

push

github

web-flow
Commitments can be scoped to specific sensors, binding their aggregate flow (#2295)

* feat: commitments can be scoped to specific sensors, binding their aggregate flow

A flex-context commitment gains an optional 'sensors' field: instead of
binding each device of the matching commodity separately, the commitment
binds the aggregate flow of the devices whose power sensors are listed,
as one grouped commitment (device_group machinery). Useful to commit a
band on a subset of devices, e.g. an aFRR upward-regulation band on a
site's e-heaters (aggregate consumption >= band, deviation penalized).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016MLCUiSdXDqDBmg8GbYp1B

* docs: changelog entry for sensor-scoped commitments (#2295)

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_015qxM7UZ5wHTz3ftz1Mf9yy
Signed-off-by: F.N. Claessen <felix@seita.nl>

* feat: allow scoping a commitment to a group (alongside the sensor list)

Follow-up on #2295. A commitment's scope can now be given as a 'group' reference
(the members of an electrical group, reusing group_to_devices) in addition to the
raw 'sensors' list; at most one of the two (schema-validated). A group scope
includes the group's inflexible members (total node flow), whereas a sensors
scope binds the listed flexible devices only -- documented on the schema field and
the resolver. Also: validate that a scoped set shares one commodity, tag scoped
commitments with provenance='custom' (was missing), and give each a unique
device_group label so same-named commitments never merge.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01TaMepbxRYzJxQKFtu6Hq4p
Signed-off-by: F.N. Claessen <felix@seita.nl>

* fix: pin a scoped commitment's commodity to its scoped devices; tests + comment tidy

Addresses Copilot's review on #2295:
- A scoped commitment now takes... (continued)

37 of 38 new or added lines in 3 files covered. (97.37%)

128 existing lines in 2 files now uncovered.

16343 of 19620 relevant lines covered (83.3%)

0.83 hits per line

Uncovered Changes

Lines Coverage ∆ File
1
91.35
0.12% flexmeasures/data/models/planning/storage.py

Coverage Regressions

Lines Coverage ∆ File
98
91.35
0.12% flexmeasures/data/models/planning/storage.py
30
93.74
0.09% flexmeasures/data/schemas/scheduling/__init__.py
Jobs
ID Job ID Ran Files Coverage
1 30712612355.1 01 Aug 2026 06:43PM UTC 172
83.3
GitHub Action Run
Source Files on build 30712612355
  • Tree
  • List 172
  • Changed 3
  • Source Changed 3
  • Coverage Changed 3
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Github Actions Build #30712612355
  • fcbf579e on github
  • Prev Build on main (#30657663831)
  • Next Build on main (#30712759706)
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