Change log levels for post-contingency and action messages in Fast DC Security Analysis

[p-arvy]

Please check if the PR fulfills these requirements

• The commit message follows our guidelines
• Tests for the changes have been added (for bug fixes / features)
• Docs have been added / updated (for bug fixes / features)
• A PR or issue has been opened in all impacted repositories (if any)

Does this PR already have an issue describing the problem?

No, but the development is based on the collaborative work of #1169, aiming to improve the performance of the fast DC SA.

What kind of change does this PR introduce?

In default and fast DC security analyses, the logs indicating the start and end of a post-contingency or post-operator strategy simulation are at the INFO level. For the fast DC SA, these logs are changed to the DEBUG level.

What is the current behavior?

Currently, the logs are displayed via method calls defined in the AbstractSecurityAnalysis class, which log at the INFO level. This represents about 5% of the CPU time for a fast DC SA run, and slows down the total execution time.

Since the computation cost is roughly the same for all contingencies in fast DC SA, these logs should be displayed at a higher level of detail.

What is the new behavior (if this is a feature change)?

The logging methods in the AbstractSecurityAnalysis class have been modified so that the log level is configurable. In the fast DC SA, the log level is now set to DEBUG, which makes the logs cleaner and improves performances.

The DEBUG level was chosen to keep the logs consistent with those related to active power distribution, when overriding pre-contingency states in the fast DC SA (the following logs are from the unit test WoodburyDcSecurityAnalysisWithActionsTest.testSaDcPhaseTapChangerTapPositionChangeWithConnectivityBreak).

Does this PR introduce a breaking change or deprecate an API?

• Yes
• No

If yes, please check if the following requirements are fulfilled

• The Breaking Change or Deprecated label has been added
• The migration steps are described in the following section

What changes might users need to make in their application due to this PR? (migration steps)

To enable the display of detailed logs for post-contingency and post-operator strategy simulations in fast DC Security Analysis, you can set the com.powsybl.openloadflow.sa.AbstractSecurityAnalysis logger to DEBUG in your logging configuration file. For better performance, it is recommended to avoid enabling these logs. It should be used only when needed for debugging or detailed analysis.

Other information:

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
100.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud