The security analysis module only enables to simulate contingencies, but not remedial actions.
What is the expected behavior?
The security analysis API of powsybl-core now enables the user to define actions and strategies linking contingencies to actions.
We should provide a python binding for those new input data.
WARNING: we should in pypowsybl to have one method per elementary action. Not like in Java a too general action (for instance HvdcAction) but small actions dedicated to business action.
Also results have to be updated to get post action status and violations
What is the motivation / use case for changing the behavior?
Being able to simulate corrective remedial actions through the security analysis API.
Feature.
The security analysis module only enables to simulate contingencies, but not remedial actions.
The security analysis API of powsybl-core now enables the user to define actions and strategies linking contingencies to actions. We should provide a python binding for those new input data.
The API could be something like:
WARNING: we should in pypowsybl to have one method per elementary action. Not like in Java a too general action (for instance HvdcAction) but small actions dedicated to business action.
Also results have to be updated to get post action status and violations
Being able to simulate corrective remedial actions through the security analysis API.