Manage a VoltageLevelFilter in GeographicalLayoutFactoryto optimize Node position computation - #821
Draft
sBouzols wants to merge 1 commit into
Draft
Conversation
… parameter to the GeographicalLayoutFactory constructor to avoid a large value for `missingPositions` on large networks when we need only some positions for a portion of the total voltageLevels Signed-off-by: sBouzols <sylvain.bouzols@gmail.com>
sBouzols
marked this pull request as draft
June 12, 2026 12:37
|
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
2 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
What kind of change does this PR introduce?
feature
What is the current behavior?
Add an optional
VoltageLevelFilterparameter to theGeographicalLayoutFactoryconstructor to avoid a large value formissingPositionswhich implies a long computation of missing positions on large networks when we need only some positions for a portion of the total voltageLevels.What is the new behavior (if this is a feature change)?
Now, position computation is implemented considering the given VoltageLevelFilter
Does this PR introduce a breaking change or deprecate an API?
What changes might users need to make in their application due to this PR? (migration steps)
No migration needed.
Add a VoltageLeveFilter to the constructor to optimize position computation for large networks