Docs/commitments section

[Flix6x]

Description

• Start documentation section on Commitment concept
• Added changelog item in documentation/changelog.rst

Look & Feel

How to test

Just visit the latest docs build, or if that is failing due to an unrelated issue, run make update-docs and visit http://localhost:5000/ui/static/documentation/html/concepts/commitments.html.

Further Improvements

Grouping over devices is ongoing work in #1934.

[read-the-docs-community]

Documentation build overview

📚 flexmeasures | 🛠️ Build #31459243 | 📁 Comparing 37d44d4 against latest (1e6409f)

🔍 Preview build

Show files changed (5 files in total): 📝 4 modified | ➕ 1 added | ➖ 0 deleted

File	Status
changelog.html	📝 modified
index.html	📝 modified
api/v3_0.html	📝 modified
concepts/commitments.html	➕ added
concepts/device_scheduler.html	📝 modified

[nhoening]

Thanks for working on this!

As you would probably expect from me, my comments are mostly about making this more useful to readers, mostly structuring.

I also would like one more hands-on example to show users the added modeling power they could have from this concept.

Oh, we should also add a note that we hope to make commitments a feature in the flex-context editor.

[nhoening]

Thanks, great stuff!

I added the TOC and worked on a few text blocks myself, but no technical items.

[nhoening]

Two questions @Flix6x :

• The _type field is explained in theory, but no examples contain it. Why?
• Is there a relationship between the number of commitments and the time it takes the optimizer to find a solution?

[Flix6x]

For the first question: I think we only exposed the "each" type commitments in the commitments field for now. And I think we might soon revisit the topic of (time) groupings based on ongoing work on device groupings.

[nhoening]

Okay so adding a small note to that effect is what I'll do for now, then merge.