Christian Bertsch

> @chrbertsch I cannot find the ticket you mentioned above. Can you please send me the ticket number? Thanks, I seem not to have sent the ticket mentioned above. I...

FMI Design Webmeeting: - Agreement, plesae create a PR @klausschuch

FMI Design Webmeeting: Karl: the FMU should simulate until the sum of the provided time + timestep Klaus: I think the standard is clear, but there seems to be no...

Discussion: Pierre: Perhaps Variable communication stepsize could be optional Pierre: We could drop the "ECU" part, SIL could require variable stepsize, Matthias: an ECU profile could support SIL/HIL Matthias: We...

This is related to modelica/fmi-standard#1439. Without such extensions, SE seems mainly to be usable for realtime simualtion, and this should be clearly stated.

Regular Design Meeting: Andreas: what should we write in the standard? Christian: A short version could be "use SE only for realtime or you should very well know what you...

> Not even optional, I think. Same goes for "Resizable Parameter Arrays" I would consider "Resizable Parameter Arrays" arrays as recommended. Same for tunable parameters.

Discussion: Kaska: We could have a basic CS, "middle" and advanced CS Profile Pierre: if the basic only contains feature that are mandatory anyway, it is not necessary. We could...

Discussion: Kaska: I agree that we should concentrate on FMI 3.0 We should go for more application specific profiles. Matthias: application speficific names are often not very general. Pierre: the...

> What about "Dynamics Controller Profile"? I think we should move the same features as above to recommended. Hm. Currently the "Dynamics Controller Profile" mentions CS and ME specific features....