Nicolas Pierre

Hello @geofjamg and @flo-dup I'm basing the dynawaltz integration on the powsybl-dynawo api. In the given part of the example, you want to add dynamically events with their timestep :...

I rebased on main, I saw that the omega_ref is automaticaly mapped to every synchronized generator. Do you confirm that the user will never have to map omega_ref ?

Also I made a branch on pypowsyb-notebooks with an example to run. All data asssociated (config, network and .par files) is provided. Specific branch is [here](https://github.com/powsybl/pypowsybl-notebooks/tree/dynawaltz)

Hello, some changes from this morning broke my compilation. I see that the generators models have changed completly. Can you confirm that GeneratorSynchronous and GeneratorFictious are the new mapping for...

I updated the mappings to `GeneratorSynchronous` variants already implemented. They now use the `GeneratorSynchronous` class. I also created a `DynamicMappingAdder` for `GeneratorSynchronous`, it allows to add via dataframe different types...

I also updated the events mapping with the new eventTime and their arguments. There are compilations errors due to commits on main.

Some information about some changes under the hood: - I moved a Dataframe function `createSeriesMetadata` from NetworkCUtil to CTypeUtil, as it is not specific to Network and i needed it...

I have some issues with the checkstyle plugin with some of the new syntax offered with the update to java 17. The commit bfe1cfd allows me to pass the checkstyle...

I agree that we should not allow calling the setter if this has no impact on the config loaded. It is easy to know if it was loaded since the...