Common interface AbstractKiteModels for all kite power system models

[ufechner7]

From the beginning the idea was to use a common interface for all models, so that we can re-use examples, tests, controllers, loggers and viewers as much as possible. The interface shall allow mixed system simulations using discrete time controllers and continues time models.

How can you define an interface in Julia? Well, it is just one or more (type) and some functions, operating on this type.

You can find the current state of discussion here: OpenSourceAWE/KiteUtils.jl#90

So far just two types and three functions:

• the abstract type AbstractKiteModel; all concrete implementations (currently KPS3, KPS4, KPS5 and SymbolicAWESystems) should be subtypes of this type
• the concrete type SysState which stores the result of one time step of the simulation
• the functions init!, next_step! and update_sys_state

The interface shall be defined in KiteUtils.jl and be implemented in KiteModels.jl and SymbolicAWEModels.jl (perhaps more). An advantage of having the models in different packages could be reduced load and compilation times, if you need only one of them. And reduced sizes of the system image (if you need to deploy the model).

Perhaps more functions, like some of the input and output functions documented here will be added. This needs further discussions, because we would like to keep the interface as thin as possible.

I started to write some tests for this interface, but that will need some more time before they are completed.

[1-Bart-1]

find_steady_state! should be part of this interface as well

[ufechner7]

I don't agree. The main reason to define a common interface is that it allows to use the same controllers or examples with different kites. So far I am not aware of any example or controller that needs to explicitly call find_steady_state!.