Christian Bertsch

Klaus: The pseudo-code in https://fmi-standard.org/docs/3.0.1/#algebraic-loops already contains a fixed-point iteration The steady state calculation is a use case, that could be handled with the exisiting mechanisms

FMI Design Meeting: Klaus: Add non-normative text explaining the separation between "definition and simulation phase" as defined by Andreas! Many colleagues got confused about this. The "information flow" of clocks...

FMI Design Webmeeting: Torsten S: e.g. you could import an FMU in Simulink without using the FMI headers or API. This does not replace eFMI, but is the missing link...

FMI-Design meeting: Pierre: How many tools support this? Torsten: We should start creating a prototype before including it in the standard Pierre: How many tools are supporting adjoint derivatives? Christian:...

Comment: this could also been in a layered standard, that defines new additional functions. If it shall be included in a minor version a working group should work on a...

Design Meeting: Pierre: For efficient Co-Simulation we need double buffering. You want to run the FMUs in parallel. Thus we need double buffers, otherwise you do not get a benefit....

Ah, one has to adapt this in the Word document properties: 

TorstenS: If you do not take a copy of the function pointers, you can run into trouble. Andreas: "The struct contains pointers to functions provided by the environment to be...

Fixed with https://github.com/modelica/fmi-standard/pull/1931

FMI Design Meeting: Klaus: I think this is a reminder of a previous definition of clocks. (This might be a problem of our usage of "input" and "output" clocks, resp....