Feature request: startup penalty

[werdnum]

Feature request: startup penalty

[davidusb-geek]

Turning on the option to make it a continuous load with just one startup is not an option for you?

[werdnum]

It’s an option, but not the preferred one. Starting up twice is fine, but it needs to be a big enough win to justify it. — Andrew Garrett

…

On Wed, 1 May 2024 at 22:11, David ***@***.***> wrote: Turning on the option to make it a continuous load with just one startup is not an option for you? — Reply to this email directly, view it on GitHub <#261 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACCFXSMHZOQNKASJXTAQTLZADLXTAVCNFSM6AAAAABGT3VWX6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOBYGM4DAMBQHA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[werdnum]

I have this somewhat working in a branch. Want to clean it up before sending a PR.

[davidusb-geek]

Hi, ok nice feature!
The annoying part will be to add a new user-defined input variable to control this.
I think that by default no penalty should be applied on the number of startups. Then if the user desires as it was your case, this option can be activated.
This has been a constant struggle, add parameters so that this optimization can be highly configurable, but at the same each new parameter adds more complexity and the people complain about how all this is hard to setup.
But go ahead these are nice features. Try to add some lines to test_optimization.py to quickly test the desired/expected behavior of the feature.

[davidusb-geek]

This is included in the just released new version.
Closing this for now but reopen if eneded.