-
Notifications
You must be signed in to change notification settings - Fork 50
Migration guide v7.1.0
Downstream projects should:
-
Check in their versionable extensions' serializers/deserializers (classes extending AbstractVersionableNetworkExtensionSerDe) that a
SerDeVersionvalue supports the new version (1.15) (usually, at least aSerDeVersionhas itsmaxIidmVersionExcludedattribute set tonull. In this case, there is nothing to do the the SerDe.); -
Upgrade the version in their XIIDM / JIIDM unit test files corresponding to the current version:
-
For ".xiidm" or ".xml" files: replace
xmlns:iidm="http://www.powsybl.org/schema/iidm/1_14"withxmlns:iidm="http://www.powsybl.org/schema/iidm/1_15"; -
For ".json" or ".jiidm" files: replace
"version" : "1.14"with"version" : "1.15".
-
Package com.powsybl.cgmes.shorcircuit was renamed into com.powsybl.cgmes.shortcircuit. (Fixes "short" )
-
DCLinkUpdate.DefaultDatarecord has 2 new attributesdouble poleLosses1anddouble poleLosses2. - CGMES conversion's
com.powsybl.cgmes.conversion.elements.transformers.TapChangerclass has no moresetSolvedTapPosition(Integer)andInteger getSolvedTapPosition()methods.
Custom IIDM implementations should adapt to the updated AC/DC Converters validation rules tested in IIDM TCK:
com.powsybl.iidm.network.tck.AbstractAcDcConverterTest#testCreationErrorcom.powsybl.iidm.network.tck.AbstractAcDcConverterTest#testTwoAcTerminals
If you defined your own IIDM implementation, you should:
- Write your own implementations of
DroopCurveandDroopCurveAdder - Implement the following methods in your
AcDcConverterimplementations:DroopCurveAdder newDroopCurve()DroopCurve getDroopCurve()