Docs/commitments section #1849
Docs/commitments section #1849
Conversation
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
…ontext Signed-off-by: F.N. Claessen <felix@seita.nl>
…formulation Signed-off-by: F.N. Claessen <felix@seita.nl>
Documentation build overview
Show files changed (4 files in total): 📝 3 modified | ➕ 1 added | ➖ 0 deleted
|
Signed-off-by: F.N. Claessen <felix@seita.nl>
Signed-off-by: F.N. Claessen <felix@seita.nl>
nhoening
left a comment
nhoening
left a comment
There was a problem hiding this comment.
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.
| -------- | ||
|
|
||
| A **Commitment** is the economic abstraction FlexMeasures uses to express | ||
| market positions and soft constraints (preferences) inside the scheduler. |
There was a problem hiding this comment.
I would quickly list two or three examples right at the start, to let the reader imagine why this concept applies to them.
Market positions:
- passive imbalance
- PPAs
- gas price baseline
Soft constraints:
- contracted (consumption|production) capacity
- Previous peaks
- CO2 levels
| -------- | ||
|
|
||
| A **Commitment** is the economic abstraction FlexMeasures uses to express | ||
| market positions and soft constraints (preferences) inside the scheduler. |
There was a problem hiding this comment.
| market positions and soft constraints (preferences) inside the scheduler. | |
| market positions and soft constraints (preferences) inside the scheduler. | |
| They are a powerful modeling concept used in current flex-context fields, but can also model new circumstances. |
|
|
||
| A **Commitment** is the economic abstraction FlexMeasures uses to express | ||
| market positions and soft constraints (preferences) inside the scheduler. | ||
| Commitments are converted to linear objective terms; all non-negotiable |
There was a problem hiding this comment.
I would tell the reader what this document delivers ("This document will explain what commitments are on a technical level, and then give examples how the scheduler uses them and how you can create your own commitments in the flex-context to great effect.")
I suggested a few section headers here, maybe include a TOC.
Then, start a subsection here: "What is a commitment?"
| interlocks) are expressed separately as Pyomo constraints in the scheduling | ||
| model. If a “hard” behaviour is required from a commitment, assign very large | ||
| penalty prices, but prefer modelling non-negotiable limits as Pyomo constraints. | ||
|
|
There was a problem hiding this comment.
New section: "How FlexMeasures uses commitments in the scheduler"
|
|
||
| - *Fields used*: ``consumption-capacity`` and ``production-capacity`` (baselines), ``consumption-breach-price`` (upwards-deviation price, with 0 downwards) and ``production-breach-price`` (downwards-deviation price, with 0 upwards). | ||
| - *Commitment*: FlowCommitment with either baseline and corresponding prices. | ||
|
|
There was a problem hiding this comment.
I suggest that we add a new section here: "How you can use commitments: An example"
Then provide a flex context example with some price blocks maybe - whatever comes off easy.
Add a few words how this would affect the schedules that are being made.
(so far, the examples are only from the internal use of commitments)
| - peak/excess limits (``site-peak-production``, ``site-peak-production-price``, etc.) → dedicated peak FlowCommitment(s); | ||
| - storage-related fields (``soc-minima``, ``soc-minima-breach-price``, etc.) → StockCommitment(s). | ||
|
|
||
| A short example |
There was a problem hiding this comment.
| A short example | |
| How the scheduler interpretes commitments: A short example |
(I don't really understand who benefits from this section - hosts, FlexMeasures devs?)
| interlocks) are expressed separately as Pyomo constraints in the scheduling | ||
| model. If a “hard” behaviour is required from a commitment, assign very large | ||
| penalty prices, but prefer modelling non-negotiable limits as Pyomo constraints. | ||
|
|
There was a problem hiding this comment.
Maybe the grouping section can be here already.
Description
Commitmentconceptdocumentation/changelog.rstLook & Feel
...
How to test
...
Further Improvements
...
Related Items
...
Sign-off