maestro
maestro copied to clipboard
INTO-CPS-Association
Maestro a Co-Simulation Orchestration Engine
Currently the FMUs are defined in both the environment.json and the MaBL spec. For example: ``` "fmus": { "{x1}": "target/test-classes/watertankcontroller-c.fmu", "{x2}": "target/test-classes/singlewatertank-20sim.fmu" }, ``` and ``` FMI2 tankcontroller = load("FMI2",...
Currently the interpreter plugins are hardcoded in the evaluation of loadExp. Covert it to a fashion similar to expansion plugins.
Recently I got handed an overture project. Due to a platform specific error the model failed on initialization. The current error message provides very little detail in to the cause...
Make it obvious what is part of the unfolding Currently the spec does not contain any information on underlying configuration or framework. **The task is to add support for the...
In some cases it could be useful not to unfold everything until just before execution. For example, for DSE, it would be useful with a spec that is only folded...
Current the topological sort and FMU initialisation takes place in the simulation phase. Conceptually, it makes more sense to do this in the initialisation phase
The release contains the wrong jar file for the COE it should be the one with dependencies
Add the following to the initialise description: - The request uses the post method - The return
Metadata
Owner
Metadata
Maestro a Co-Simulation Orchestration Engine