maestro
maestro copied to clipboard
Maestro a Co-Simulation Orchestration Engine
When defining co-simulation scenarios there are different approaches. **Derived** One of these is to define properties on the FMUs and their respective ports and then automatically calculate the given order...
Upon executing the test part2_json_parse some of the resulting intermediate files are the exact same: spec00000, spec00001, and spec00002.
When using the CLI the following warning is displayed: `WARNING: sun.reflect.Reflection.getCallerClass is not supported. This will impact performance.`
Currently comments are removed during parsing. This should not be the case.
Document expansion plugins Document runtime plugins Document basic example hereamong FMI2 interface
Implement stabilisation in the initialization plugin and document its conceptual behaviour. A runtime module has been created to support the isClose behaviour: https://github.com/INTO-CPS-Association/maestro/commit/4f717488ffb21a421ba6af0b781d3d5fc9934c84 In order to use this behaviour one...
The API can be annotated with swagger annotations that provide descriptions of the operations, model and similar. For example, see the picture below:  These comments are realised via ```@ApiModelProperty(value...
See https://github.com/INTO-CPS-Association/maestro/blob/ctm/139-compositionality/maestro/src/test/java/compositionExampleTest.java as an example of composition that gives this output: ``` Jacobi StepAlgorithm - Fixed - max size 0.5 FMU-jac1 Gauss-Seidel StepAlgorithm - Variable - max size 0.5 FMU-gauss1...
Examples are: fix_recovering variable, discardObserved variable and fix_recoveryStepSize