powsybl-open-loadflow
powsybl-open-loadflow copied to clipboard
Reports from reporter when using operator strategy are unexplicit
Describe the current behavior
When setting up a reporter for the security analysis and using operator strategies, reports from the actions applications are not properly named and separated from the post contingency part.
Here is an example with an action on load after contingency 'First contingency' :
`+
+ AC security analysis on network 'sim1'
+ Network CC0 SC0
+ Post loading processing
Network has 4 buses and 4 branches
Network balance: active generation=1214.0 MW, active load=600.0 MW, reactive generation=0.0 MVar, reactive load=200.0 MVar
+ Pre-contingency simulation
AC load flow complete with NR status 'CONVERGED'
+ Outer loop Distributed slack on generation
Iteration 0: slack bus active power (-606.5596837558763 MW) distributed in 1 iterations
Iteration 1: slack bus active power (-1.8792855272990572 MW) distributed in 1 iterations
Iteration 2: already balanced
+ Outer loop Voltage monitoring
+ Outer loop Reactive limits
+ Outer loop Distributed slack on generation
Iteration 2: already balanced
+ Outer loop Voltage monitoring
+ Outer loop Reactive limits
+ Post-contingency simulation 'First contingency'
AC load flow complete with NR status 'CONVERGED'
AC load flow complete with NR status 'CONVERGED'
+ Outer loop Distributed slack on generation
Iteration 0: slack bus active power (5.802308970041903 MW) distributed in 1 iterations
Iteration 1: already balanced
+ Outer loop Voltage monitoring
+ Outer loop Reactive limits
+ Outer loop Distributed slack on generation
Iteration 1: already balanced
+ Outer loop Voltage monitoring
+ Outer loop Reactive limits
+ Outer loop Distributed slack on generation
Iteration 0: slack bus active power (157.40550268841523 MW) distributed in 1 iterations
Iteration 1: already balanced
+ Outer loop Voltage monitoring
+ Outer loop Reactive limits
+ Outer loop Distributed slack on generation
Iteration 1: already balanced
+ Outer loop Voltage monitoring
+ Outer loop Reactive limits
Describe the expected behavior
Reports from the action application need to be properly separated from the post contingency report.
Describe the steps
No response
Environment
No response
Relevant Log Output
No response
Extra Information
No response