Beta test for calculate regions feature

[springfall2008]

I've added a new feature on 'main' called Calculate Regions optimisation (which is off by default).

For me it seems to improve the Agile optimisation quite a bit, please can someone else test it?

[AndrewNalty]

Happy to give it a go! Do I need autoupdate off if I'm installing this manually?

What do regions do?..

[springfall2008]

Turn off auto update and select main from the version list.

regions is just an extra optimisation step to improve the plan

[AndrewNalty]

Certainly looks to be working fine but no obvious changes to my plan

[springfall2008]

So turning it on and off has no impact

[AndrewNalty]

[AndrewNalty]

Hadn't actually given it a chance to run! Sorry

[mpartington]

I can't test unfortunately as not on agile, but if it's successful, would it be worth consolidating the different plan tweaks currently available?

For example, this could be renamed 'agile optimisation' (or similar), so it's really obvious what it does, then maybe remove the others as can't imagine a second pass would normally be required on flux, go or intelligent go.

[gcoan]

calculate region optimisation = False:

calculate region optimisation = True

Predbat has coloured a lot of the import slots a different colour, and whilst the charge periods & target soc's look the same, the resultant plan is 9p cheaper y 8am tomorrow.

Just for comparison, here's 7.14.33 that I was on previously, which is half way between the two. But some of the load figures are different that main & calculate region optimisation=true

And might as well, 7.14.34:

and back to main with calculate region optimisation=True, its cheaper again:

but as it ticked over to 15:30, the cost to 08:00 tomorrow morning has jumped up again by 20p:

@springfall2008 its hard to see whether this latest tweak option is having any benefit or not. The load figures seem to be slightly different each run and the cost changed when it goes over a half hour boundary. Other that more is coloured red rather than green, the actual plan looks the same

[gcoan]

Next run, the cost to tomorrow 8am has gone up again. It can't necessarily be that we have got load on now and that's changing the figures, as the cost to 16:00 today is remaining constant at £4.30, but the projected cost into tomorrow is changing

Here's the logfile if its any use
appdaemon (13).log

[AndrewNalty]

At 04.30 on both plans I am 100% SOC with calculate regions 20p cheaper

[springfall2008]

I found a bug that would cause the old colouring and suchlike and pushed a fix to main, so maybe update and try again?

[gcoan]

latest main version. region optimisation=True

region optimisation=False

20p cheaper with region optimisation False :-(

as it ticked round 16:30, the price to 8:00 jumped up again by 14p:
(still region opt=false)

setting region optimisation to True again, its 25p cheaper:

Whilst I was looking at the different plans, trying to see what was different (not a lot except the second run with region optimisation=True didn't have a discharge slot), Predbat has made another run and the price to 8am has gone back up again:

So in summary, the latest main isn;t colouring things red as much.
Financially it looks like the region optimisation makes a small positive financial contribution but its hard to be absolutely clear on this as the price to a fixed point in time keeps changing on subsequent predbat runs anyway