CGMES: Deterministic CGM subnetworks import order - #4080
Open
jeandemanged wants to merge 3 commits into
Open
Conversation
Signed-off-by: Damien Jeandemange <damien.jeandemange@artelys.com>
5 tasks
…e too Signed-off-by: Damien Jeandemange <damien.jeandemange@artelys.com>
NathanDissoubray
approved these changes
Aug 31, 2026
|
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?
When importing a CGM with subnetworks, the subnetworks are in a random order. The same import when repeated leads to different IIDM and reports because of different subnetworks loading order.
What is the new behavior (if this is a feature change)?
Subnetworks are always imported in deterministic order, depending on
iidm.import.cgmes.cgm-with-subnetworks-defined-byparameter:FILENAME: IGM name used as sorting keyMODELING_AUTHORITY: modeling authority used as sorting keyThe PR also fixes a bug with the
FILENAMEmethod: an IGM name that's a substring of another (e.g.Galiavs.HVDC-Nordheim-Galia) caused name.contains(igmName) to pull the composite IGM's files into the simple IGM's subnetwork too, producing a merge failure (equipment already exists).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)
Other information: