Setting power fails @ 100%

[Wobbly74]

In the development branch, when using elements which end up with various fractional percentages of the overall power this sometimes ends up with not being able to set the power to 100%, due to the precision of using a float for the calculation. This is easily replicated when setting up 2 elements, one with 3000w the other with 1500w. This ends up with a final powersum array value of 99.999999999 which causes the searchsorted function call in calculate_individual_actor_power to fail with an index out of range when trying to set the power to 100. I've worked around this simply at the moment by just always overriding the last powersum array element to always be 100. Apart from that the newer version of the plugin seems to work ok at first test, as I want to use this plugin to restrict the number of elements used when reaching a boil.

[avollkopf]

The development branch is not maintained, since I detected plenty of issues with the last tests one year ago and basically nobody was using it. Currently, there are no resources for further development. We need volunteers :-)

[Wobbly74]

Do you have a list of the issues uncovered with it?Cheers,Neil. On 5 Jul 2023, at 12:08 am, Alexander Vollkopf ***@***.***> wrote: The development branch is not maintained, since I detected plenty of issues with the last tests one year ago and basically nobody was using it. Currently, there are no resources for further development. We need volunteers :-) —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: ***@***.***>

[avollkopf]

Not really, since it's about a year ago and nobody really tested it