libcimpp issueshttps://git.rwth-aachen.de/acs/public/cim/cimpp/libcimpp/-/issues2020-10-30T20:28:23+01:00https://git.rwth-aachen.de/acs/public/cim/cimpp/libcimpp/-/issues/53Pointer attributes not initialised to null2020-10-30T20:28:23+01:00Richard MarstonPointer attributes not initialised to nullPointer attributes need to be initialised to null in the constructor so that applications using the library can check if the pointer is valid.Pointer attributes need to be initialised to null in the constructor so that applications using the library can check if the pointer is valid.https://git.rwth-aachen.de/acs/public/cim/cimpp/libcimpp/-/issues/50Create Github build pipeline2020-09-25T10:28:08+02:00Richard MarstonCreate Github build pipelinehttps://git.rwth-aachen.de/acs/public/cim/cimpp/libcimpp/-/issues/48Support multiple versions of RDFS2020-09-25T10:10:53+02:00Richard MarstonSupport multiple versions of RDFShttps://git.rwth-aachen.de/acs/public/cim/cimpp/libcimpp/-/issues/47Create mapping file for namespaces to CIMPP in old versions2020-05-12T16:50:14+02:00Richard MarstonCreate mapping file for namespaces to CIMPP in old versionshttps://git.rwth-aachen.de/acs/public/cim/cimpp/libcimpp/-/issues/49Automated builds of dpsim broken2020-05-08T16:21:37+02:00Richard MarstonAutomated builds of dpsim brokenDPSim pulls libcimpp from github. Github does not know about cim-codebase-generator. The cim-codebase-generator submodule in libcimpp has broken the dpsim build. It needs to be removed.DPSim pulls libcimpp from github. Github does not know about cim-codebase-generator. The cim-codebase-generator submodule in libcimpp has broken the dpsim build. It needs to be removed.https://git.rwth-aachen.de/acs/public/cim/cimpp/libcimpp/-/issues/43Support CGMES and CIM namespaces2020-05-05T22:34:29+02:00Jan DinkelbachSupport CGMES and CIM namespacesresolve CIM specific code, e.g. references to CIM classes, such as
- IEC61970::Base::Core::IdentifiedObject (e.g. in CIMContentHandler.cpp)
- CGMES::IdentifiedObjectresolve CIM specific code, e.g. references to CIM classes, such as
- IEC61970::Base::Core::IdentifiedObject (e.g. in CIMContentHandler.cpp)
- CGMES::IdentifiedObjectRichard MarstonRichard Marstonhttps://git.rwth-aachen.de/acs/public/cim/cimpp/libcimpp/-/issues/46VoltageLevel.Substation cannot be resolved2020-04-30T13:12:24+02:00Markus MirzVoltageLevel.Substation cannot be resolvedFrom the CIM++ docs it seems that VoltageLevel does not have a pointer to Substation but vice versa https://cim.fein-aachen.org/libcimpp/doc/IEC61970_16v29a/classIEC61970_1_1Base_1_1Core_1_1VoltageLevel.html
This could be the reason why...From the CIM++ docs it seems that VoltageLevel does not have a pointer to Substation but vice versa https://cim.fein-aachen.org/libcimpp/doc/IEC61970_16v29a/classIEC61970_1_1Base_1_1Core_1_1VoltageLevel.html
This could be the reason why a CIM files like the following cannot be resolved correctly
```
<cim:VoltageLevel rdf:ID="_1d86b5e7-ff8b-4475-a314-50001d6a4319">
<cim:IdentifiedObject.name>7081</cim:IdentifiedObject.name>
<cim:VoltageLevel.Substation rdf:resource="#_3FA2-2E-F1-00000000000037303831"/>
<cim:VoltageLevel.BaseVoltage rdf:resource="#_93a918b5-2b10-4473-be04-aae01d5cec31"/>
</cim:VoltageLevel>
```
Maximilian Paul KißgenMaximilian Paul Kißgenhttps://git.rwth-aachen.de/acs/public/cim/cimpp/libcimpp/-/issues/21Problem e.g. with += on CIM primitive types like Float2020-04-30T12:04:24+02:00Lukas Daniel RazikProblem e.g. with += on CIM primitive types like FloatIn case of having<br>
`IEC61970::Base::Domain::Float a,b;`<br>
following returns an compiler error because of no compatible `operator+=`:<br>
`a += b;`
Workaround:<br>
`a = a + b;`
Should be checked and fixed without overloadin...In case of having<br>
`IEC61970::Base::Domain::Float a,b;`<br>
following returns an compiler error because of no compatible `operator+=`:<br>
`a += b;`
Workaround:<br>
`a = a + b;`
Should be checked and fixed without overloading `operator+=, operator*=, ...` if possible.
Mohammad KohankhakiMohammad Kohankhakihttps://git.rwth-aachen.de/acs/public/cim/cimpp/libcimpp/-/issues/8Add namespace2020-04-30T11:49:12+02:00Daniel KnibbeAdd namespacehttps://git.rwth-aachen.de/acs/public/cim/cimpp/libcimpp/-/issues/20Enum Initialisation2020-04-30T11:47:35+02:00Maximilian Paul KißgenEnum InitialisationEvery enum needs to have a standard value. That standard value needs to be assigned by default.Every enum needs to have a standard value. That standard value needs to be assigned by default.Lukas Daniel RazikLukas Daniel Razikhttps://git.rwth-aachen.de/acs/public/cim/cimpp/libcimpp/-/issues/16Implement a logger class2020-04-30T11:44:07+02:00Daniel KnibbeImplement a logger classWe could use a logger class to log messages from the CIM parser for later inspection.We could use a logger class to log messages from the CIM parser for later inspection.https://git.rwth-aachen.de/acs/public/cim/cimpp/libcimpp/-/issues/9Include BatteryStorage2020-04-30T11:41:35+02:00Markus MirzInclude BatteryStorageWe need to include the BatteryStorage in the CIM-Parser. A CIM equivalent exists already in the SINERGIEN EA Project.We need to include the BatteryStorage in the CIM-Parser. A CIM equivalent exists already in the SINERGIEN EA Project.Lukas Daniel RazikLukas Daniel Razikhttps://git.rwth-aachen.de/acs/public/cim/cimpp/libcimpp/-/issues/33Missing values for the mRID property2019-06-06T23:21:20+02:00Subhodeep Chakrabortysubhodeep.chakraborty@rwth-aachen.deMissing values for the mRID propertyDue to some reason the parser is unable to get the UUID values for mRID property of the IdentifiedObject class. Please see the screenshot below. ![Screenshot_from_2018-02-20_17-01-34](/uploads/6000b36c01bb4536ff2bc63be103df03/Screenshot_...Due to some reason the parser is unable to get the UUID values for mRID property of the IdentifiedObject class. Please see the screenshot below. ![Screenshot_from_2018-02-20_17-01-34](/uploads/6000b36c01bb4536ff2bc63be103df03/Screenshot_from_2018-02-20_17-01-34.png)
The following file was used as input.[ModPowerSystems_MV_Grid_PQLoad.xml](/uploads/4d832ee6a1ab1795d7e33df158bf999e/ModPowerSystems_MV_Grid_PQLoad.xml)Lukas Daniel RazikLukas Daniel Razikhttps://git.rwth-aachen.de/acs/public/cim/cimpp/libcimpp/-/issues/22Error in parsing2019-06-06T23:19:46+02:00Subhodeep Chakrabortysubhodeep.chakraborty@rwth-aachen.deError in parsingLately I have been working with Distribution System networks such as the IEEE-13, and tried to parse the CIM-XML file of the same (attached) but I was not able to do it as it is throwing some error (screenshot attached[ieee13.xml](/uploa...Lately I have been working with Distribution System networks such as the IEEE-13, and tried to parse the CIM-XML file of the same (attached) but I was not able to do it as it is throwing some error (screenshot attached[ieee13.xml](/uploads/6c140b1eaa841a0b6cd3fcc7806afa31/ieee13.xml)![Unbenannt](/uploads/69deb39683b156e5d47216e8a82e39c2/Unbenannt.PNG)).https://git.rwth-aachen.de/acs/public/cim/cimpp/libcimpp/-/issues/19Error in parsing a specific package2019-06-06T23:18:50+02:00Subhodeep Chakrabortysubhodeep.chakraborty@rwth-aachen.deError in parsing a specific packageThere was an error due to some missing classes as I tried to parse a CIM-XML file (attached). Please refer to the screenshot attached ![fehler](/uploads/5e62f8196635de4fc8cd83155bbd0650/fehler.PNG)
CIM-XML file:[sample_nw.xml](/uploads/f...There was an error due to some missing classes as I tried to parse a CIM-XML file (attached). Please refer to the screenshot attached ![fehler](/uploads/5e62f8196635de4fc8cd83155bbd0650/fehler.PNG)
CIM-XML file:[sample_nw.xml](/uploads/f49bfdda5f7bd5f91c5360afb772997a/sample_nw.xml)https://git.rwth-aachen.de/acs/public/cim/cimpp/libcimpp/-/issues/35Merge working branches into master and delete old ones2018-04-08T14:07:52+02:00Maximilian Paul KißgenMerge working branches into master and delete old onesBranches that are to be merged:
-`SINERGIEN-neu`
-`EnumInitialisation`(also in CIMRefactorer)
-`alias-search-path`(also in CIMUnmarshallingGenerator)
-`exception`
Branches that are to be deleted:
-`SINERGIEN`
-`IEC61968`
-`fix-wi...Branches that are to be merged:
-`SINERGIEN-neu`
-`EnumInitialisation`(also in CIMRefactorer)
-`alias-search-path`(also in CIMUnmarshallingGenerator)
-`exception`
Branches that are to be deleted:
-`SINERGIEN`
-`IEC61968`
-`fix-windows`Maximilian Paul KißgenMaximilian Paul Kißgenhttps://git.rwth-aachen.de/acs/public/cim/cimpp/libcimpp/-/issues/36Compilation is broken2018-04-08T14:07:34+02:00Steffen Vogelstvogel@eonerc.rwth-aachen.deCompilation is brokenCommit 53378e55557c80c2eb05cc49ddce2b91f18a0fd7 breaks compilation for CIM 16v29a as it adds Singergien specific code to `16v29a/Task.cpp` which (I guess) should only be in `16v29a_SINERGIEN/Task.cpp`.
@maximilian.kissgen Can you regene...Commit 53378e55557c80c2eb05cc49ddce2b91f18a0fd7 breaks compilation for CIM 16v29a as it adds Singergien specific code to `16v29a/Task.cpp` which (I guess) should only be in `16v29a_SINERGIEN/Task.cpp`.
@maximilian.kissgen Can you regenerate the code without the Singergien classes in 16v29a?
/cc @lrazik
This issue is blocking #25Maximilian Paul KißgenMaximilian Paul Kißgenhttps://git.rwth-aachen.de/acs/public/cim/cimpp/libcimpp/-/issues/37Build code as part of the CI runs2018-04-06T12:27:58+02:00Steffen Vogelstvogel@eonerc.rwth-aachen.deBuild code as part of the CI runsTo avoid mishaps like #36, I suggest that we compile libcimpp on the CI servers for all available profiles.To avoid mishaps like #36, I suggest that we compile libcimpp on the CI servers for all available profiles.https://git.rwth-aachen.de/acs/public/cim/cimpp/libcimpp/-/issues/31Derive all CIMExceptions from a common class2018-04-06T10:30:00+02:00Steffen Vogelstvogel@eonerc.rwth-aachen.deDerive all CIMExceptions from a common classIt would be nice if we could derive all CIM related exceptions from a common class such as `CIMException`.
This would allow us to use better scoped catch clauses.It would be nice if we could derive all CIM related exceptions from a common class such as `CIMException`.
This would allow us to use better scoped catch clauses.Mohammad KohankhakiMohammad Kohankhakihttps://git.rwth-aachen.de/acs/public/cim/cimpp/libcimpp/-/issues/34Handling von alias CSV Dateien2018-03-14T10:26:54+01:00Markus MirzHandling von alias CSV DateienEs würde für uns die Sache erheblich vereinfach, wenn die CSV Dateien direkt in die Library gebaut werden. Dann wird auch dieser merge request obsolet:
https://git.rwth-aachen.de/acs/core/cim/cimpp/libcimpp/merge_requests/11
Von unserer ...Es würde für uns die Sache erheblich vereinfach, wenn die CSV Dateien direkt in die Library gebaut werden. Dann wird auch dieser merge request obsolet:
https://git.rwth-aachen.de/acs/core/cim/cimpp/libcimpp/merge_requests/11
Von unserer Seite hat das glaube ich die höchste Prioritat da wir sonst CIMpp nicht mit dem Python package von dpsim nutzen können.
Edit:
Nach Diskussionen mit @lrazik und @stvogel würde ich sagen, dass wir den von Steffen unten beschriebenen Ansatz verfolgen sollten. Allerdings sollte der Nutzer dann keine Warnung bekommen, falls keine alias Dateien gefunden werden. Die Möglichkeit einer API Funktion finde ich auch besser als das die Dateien einfach an einem bestimmten Ort liegen müssen.Steffen Vogelstvogel@eonerc.rwth-aachen.deSteffen Vogelstvogel@eonerc.rwth-aachen.de