Jan Dinkelbach

**Description to be done** Reconsider also to remove `DP_Ph1_SynchronGeneratorIter`

Currently, several components implements their own version of DQ-DP or DQ-EMT transformations. This shall be harmonized by implementation and reuse of corresponding DQ-Domain interface classes.

We have currently example files under - [examples](https://github.com/sogno-platform/dpsim/tree/master/examples) - [dpsim/examples](https://github.com/sogno-platform/dpsim/tree/master/dpsim/examples) This shall be merged to have only one place with example files. Also reconsider subfolder distinctions under - [dpsim/examples/cxx ](https://github.com/sogno-platform/dpsim/tree/master/dpsim/examples/cxx)...

- [x] Reuse the order-specific auxiliar constants in the domain specific VBR models - Example 4th order: - [EMT_Ph3_SynchronGenerator4OrderVBR](https://github.com/sogno-platform/dpsim/blob/3dc0f557d3d55ed6dc06f9333ee326fe3e59dc44/models/Source/EMT/EMT_Ph3_SynchronGenerator4OrderVBR.cpp#L66) - The same constants are also used by `DP_Ph1_SynchronGenerator4OrderVBR` and `SP_Ph1_SynchronGenerator4OrderVBR`...

The varying entries need to be set properly for this, see for example here: https://github.com/sogno-platform/dpsim/blob/758d47c4c25db49c5dfae4bd3355d40e2b90d144/dpsim-models/src/DP/DP_Ph1_ReducedOrderSynchronGeneratorVBR.cpp#L89-L91

Check use of parent methods by composite comps

2

A developer of a certain `CompositePowerComp` should implement custom behaviours for `Initialize`, `ApplySystemMatrixStamp` etc. by means of the `mnaParent...` methods and not by means of the `mnaComp...` methods of the...

We can use github file storage and link it within our documentation.