Valentin Kaisermayer
Valentin Kaisermayer
> Did #7 solve this @ValentinKaisermayer ? You mean #26?
Seems to be an MTK issue with `inputs_to_parameters!` and array variables. The `StateSpace` block is the only one using it. @baggepinnen can you have a look?
Why doesn't the downstream test fail in MTK?
> Seems like a real failure? Yes, but in MTK.
How does this work if the input would be a `Num`. See #50
If `connect` would be overloaded for `Num` it could work. `connect(sys1.output.u, sys2.input.u[1])` If this would be possible, also the need for `RealInput` and `RealOutput` beeing an `OdeSystem` would vanish.
The DC motor on its own works:  However, there is again that key not found error for other setups.
> This is doing a lot. Can this be rebased? Are there pieces that should be individual PRs? - There are some formatting changes in Electrical that could be a...
Doc strings are missing and actual tests
I meant a `# Connectors:` section in the doc strings, listing the connectors of the components. You can have a look at the doc strings in the other modules.