Skip to content

Fix EMS-level flow commitment constraints - #2355

Open
Sanjays2402 wants to merge 1 commit into
FlexMeasures:mainfrom
Sanjays2402:fix/2326-bind-ems-flow-commitments
Open

Fix EMS-level flow commitment constraints#2355
Sanjays2402 wants to merge 1 commit into
FlexMeasures:mainfrom
Sanjays2402:fix/2326-bind-ems-flow-commitments

Conversation

@Sanjays2402

Copy link
Copy Markdown

Closes #2326

Description

  • Bind priced EMS-level flow commitments to aggregate device flow
  • Add regression coverage for a two-device EMS target
  • Added changelog item in documentation/changelog.rst

Look & Feel

N/A

How to test

Run pytest flexmeasures/data/models/planning/tests/test_commitments.py.

Further Improvements

N/A

Related Items

Issue #2326


Sign-off

  • I agree to contribute to the project under Apache 2 License.
  • To the best of my knowledge, the proposed patch is not based on code under GPL or other license that is incompatible with FlexMeasures

EMS-level commitments currently create an unbounded constraint tuple, leaving their deviation variables uncoupled from device flow. Mirror grouped commitments when selecting bounds and cover aggregate scheduling with a regression test.

Signed-off-by: Sanjay Santhanam <51058514+Sanjays2402@users.noreply.github.com>
@read-the-docs-community

Copy link
Copy Markdown

Documentation build overview

📚 flexmeasures | 🛠️ Build #33736150 | 📁 Comparing d4f32fc against latest (41f692c)

  🔍 Preview build  

2 files changed
± changelog.html
± api/v3_0.html

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

EMS-level FlowCommitments generate no coupling constraint in device_scheduler

1 participant