Skip to content

Conversation

@olperr1
Copy link
Member

@olperr1 olperr1 commented Nov 19, 2025

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

What kind of change does this PR introduce?

Bug fix

What is the current behavior?

At IIDM export, when a specific topology level is specified for a voltage level, the generated file is invalid: the nodes or busses are correctly described, but the connectables may be incorrect (node attributes instead of bus/connectableBus).

What is the new behavior (if this is a feature change)?
The generated files are valid.

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)

Other information:

Fix problem with #3547

context.getWriter().writeStringAttribute("voltageLevelId" + index, context.getAnonymizer().anonymizeString(t.getVoltageLevel().getId()));
}
TopologyLevel topologyLevel = TopologyLevel.min(t.getVoltageLevel().getTopologyKind(), context.getOptions().getTopologyLevel());
TopologyLevel topologyLevel = TopologyLevelUtil.determineTopologyLevel(t.getVoltageLevel(), context);
Copy link
Member Author

@olperr1 olperr1 Nov 19, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#3614 introduces a new writeNodeOrBus() method in ConnectableSerDeUtil.
This change should be reported in it too.

@alicecaron alicecaron moved this from TODO to Approved in Release 12/2025 Nov 21, 2025
Copy link
Member

@rolnico rolnico left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@sonarqubecloud
Copy link

@rolnico rolnico merged commit ee618fc into main Nov 24, 2025
9 checks passed
@github-project-automation github-project-automation bot moved this from Approved to Done in Release 12/2025 Nov 24, 2025
@rolnico rolnico deleted the fix_vl_export_at_choosen_topology branch November 24, 2025 11:26
JacquesBorsenberger pushed a commit that referenced this pull request Nov 24, 2025
Fix export with custom voltage level topology (#3659)

Signed-off-by: Olivier Perrin <[email protected]>
jeandemanged added a commit that referenced this pull request Nov 25, 2025
olperr1 pushed a commit that referenced this pull request Nov 27, 2025
* dcNode, dcGround, dcLine, dcSwitch
* fix equipment xsd
* VSC reactive limits
* AcDcConverter pccTerminal, DC terminals P & I
* TerminalRefSerDe support for TerminalNumber
* DcNode, DcGround, DcLine, DcSwitch serde test
* LineCommutatedConverter, VoltageSourceConverter serde test
* backward (in)compatibility tests
* refactor read/write DcTerminal P&I
* doc update
* Allow setting AC/DC Converter PCC Terminal to be the converter first terminal
* DcTerminal P&I SerDe: always dcP<num> and dcI<num>
* Add control mode P_PCC_DROOP and DroopCurve Serde
* future iidm versions > 1.15 will run backward compatibility tests
* ConnectableSerDeUtil uses the new TopologyLevelUtil from #3659
* test export converter with VL TopologyLevel bus/branch

Signed-off-by: Damien Jeandemange <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

5 participants