strange schedule with peak power limits

[Ragnar-the-mighty]

I have no peak power penalty for 4 hours then I have peak power penalty (only for consumption) for the next 4 hours.

Expected behavior

• High charge in the first hours, over the "site-peak-consumption": "5.56 kW" so that all the charge is done before peak power penalty becomes active

What I got was

• The charging stay under the "site-peak-consumption": "5.56 kW" during the first 4 hours.

I have create a flexmeasures client code example so I do not have to write to much. The example print flex context and flex model. I ran the example against v0.28

peak_power_issue.py

[Flix6x]

Thank you for again including an example, these are always very helpful. I'd need to investigate more closely, but I believe the server-side implementation of the peak commitment may still be assuming a constant price over the entire planning horizon. It looks like there is still a little bit of work to support dynamic peak prices.

• I think Multiple peak consumption prices not working #1321 is the same issue.
• Also related to Reset monthly peak component #1215.

[Ragnar-the-mighty]

I think you are correct when I tested 4 hours of penalty and 4 hours without penalty it did the same thing.

[Flix6x]

@Ragnar-the-mighty Would you be able to help check whether #1835 resolves your issue?

[Ragnar-the-mighty]

@Flix6x
Thanksgiving weekend in the US, so maybe next week.

I just get the latest from main or should I use feat/multiple-peak-prices branch?

[Flix6x]

Exactly, you'd need the feat/multiple-peak-prices branch.

[Flix6x]

@Ragnar-the-mighty Do you see a chance to check now that the holiday season is over? 😄

[Ragnar-the-mighty]

@Flix6x Sorry I have been busy and testing a branch is more work that is should be in the way we have setup our environment.