A way to move Programmagle block out of experimental mode
As I understand, the programmable block was moved to experimental mode due to it's unpredictable performances strain and so, it's PCU score can't be defined.
But what if the user could define the PCU by himself?
My idea it to implement a configurable watchdog on the programmable block. This watchdog would make sure the script runs within a predefined time. Otherwise, the watchdog will stop the execution and lock the PB until recompiled.
The time limit of that watchdog would be directly linked to the PCU cost of the PB and could be adjusted at the compilation time by the user.
That way, a small airlock script that runs fast could be set to cost less PCU than an heavy inventory management scripts.
Thank you for your attention. Please tell me if this is a good or bad idea.