Save and restore only active power changes in Fast DC Security Analysis#1205
Merged
vidaldid-rte merged 21 commits intomainfrom Apr 11, 2025
Merged
Save and restore only active power changes in Fast DC Security Analysis#1205vidaldid-rte merged 21 commits intomainfrom
vidaldid-rte merged 21 commits intomainfrom
Conversation
Member
Author
|
This PR should be merged only after #1192. |
p-arvy
changed the title
p-arvy
changed the title
Base automatically changed from
connectivity-loss-in-connectivity-break-analysis
to
main
April 7, 2025 10:17
Signed-off-by: p-arvy <pierre.arvy@artelys.com>
Signed-off-by: p-arvy <pierre.arvy@artelys.com>
Signed-off-by: p-arvy <pierre.arvy@artelys.com>
…Results Signed-off-by: Hadrien <hadrien.godard@artelys.com>
Signed-off-by: p-arvy <pierre.arvy@artelys.com>
Signed-off-by: p-arvy <pierre.arvy@artelys.com>
Signed-off-by: p-arvy <pierre.arvy@artelys.com>
Signed-off-by: p-arvy <pierre.arvy@artelys.com>
p-arvy
force-pushed
the
save-and-restore-dc-states-in-fast-dc-sa
branch
from
7dcc81f to
33f85f8
Compare
Signed-off-by: Hadrien <hadrien.godard@artelys.com>
Hadrien-Godard
previously approved these changes
Apr 8, 2025
| /** | ||
| * Process the power shifts due to the loss of loads, generators, and HVDCs. | ||
| * @param balanceType the property defining how to manage active distribution. | ||
| * @param updateAcParameters a boolean to indicate if voltage/reactive dependent parameters should be updated or not. |
Collaborator
There was a problem hiding this comment.
The name updateAcParameters is confusing. Parameters usually refers to parameters that alter the simulator behaviour.
Why not updateAcQuantities ?
(the comment applies to all similar uses of the term parameter in this file (in comments for example)
Member
Author
There was a problem hiding this comment.
Applied. Thanks for the suggestion.
Signed-off-by: p-arvy <pierre.arvy@artelys.com>
Signed-off-by: p-arvy <pierre.arvy@artelys.com>
vidaldid-rte
approved these changes
Apr 10, 2025
|
Hadrien-Godard
approved these changes
Apr 11, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Please check if the PR fulfills these requirements
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 fast DC SA, the application of
LfContingencyin cases where a load/generator is lost, preceding the calculation of the right-hand side override (before computing post-contingency states withWoodburyEngine) has been modified for better performance.What is the current behavior?
In the current state of fast DC SA, when a contingency causes the loss of a generator/load, the associated
LfContingencyis applied before computing the right-hand side override (preceding the post-contingency state calculations).To avoid disrupting subsequent computations, a
NetworkStateis saved before the application and restored afterward. This is done for each contingency. On an IGM FR with approximately 600 generator contingencies, this accounts for around 30% of the computation time.What is the new behavior (if this is a feature change)?
Only DC values related to generators, loads, and HVDCs need to be modified, and therefore saved and restored. The saving/restoring of a
NetworkStateis replaced by saving/restoringBusDcStates. The application of theLfContingencyis also modified to change only these values.Comparing against the same case, the post-contingency state computation time is reduced of ~20%.
Does this PR introduce a breaking change or deprecate an API?
If yes, please check if the following requirements are fulfilled
What changes might users need to make in their application due to this PR? (migration steps)
Other information: