fmi-guides icon indicating copy to clipboard operation
fmi-guides copied to clipboard

Published 20 hours ago • verified publisher icon modelica

Changes to "dynamics profile"

Open chrbertsch opened this issue 2 years ago • 7 comments

Move from required to recommended:

  • Tunable Parameters
  • Store/Restore FMU State
  • Serialize/Deserialize FMU State
  • String Inputs/Outputs
  • Resizable Input/Output Arrays
  • Resizable Input/Output Arrays with Size-Dependencies
  • Resizable Parameter Arrays
  • Resizable Parameter Arrays with Size-Dependencies

Remove as the shall be supported anyway by all FMI3 FMUs:

  • New Integer Types

chrbertsch avatar Jun 27 '22 06:06 chrbertsch

What about "Dynamics Controller Profile"? I think we should move the same features as above to recommended.

andreas-junghanns avatar Jun 27 '22 09:06 andreas-junghanns

Compared to all the other features that are required, why is directional derivative only recommended?

KarlWernersson avatar Jun 27 '22 10:06 KarlWernersson

To motivate: directional derivative, it is needed to efficiently solve algebraic loops which easily can occur when tightly connecting physical models in dynamic simulation.

edit. Mainly for ME, although could also be sued for hybrid co-simulation during event mode

KarlWernersson avatar Jun 27 '22 11:06 KarlWernersson

Proposal from design meeting 2022-06-27:

  • Split into ME-specific and CS-specific Profile:
    • Drop Store/Restore for ME, add Directional Derivatives for ME as required, remove CS-specific features
    • Keep Store/Restore for CS as is,
  • Remove CS with Clocks here, should be enough in Dynamics Controller
  • Remove String I/O (-> binary I/O is likely enough)
  • Drop Resizable I/O Arrays with and without Size-Dependencies from Profile, might need a new profile for this specific use-case.
  • Drop Binary I/O

pmai avatar Jun 27 '22 14:06 pmai

Proposal from design meeting 2022-06-27:

  • Remove String I/O (-> binary I/O is likely enough)

Good.

MBlesken avatar Jan 30 '23 08:01 MBlesken

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. Shouldn't we not better to decide for one of them?

chrbertsch avatar Feb 01 '23 20:02 chrbertsch

Discussion: Pierre: we can discuss whether to split into ME and CS or how to present this Kaska: We should make resizable arrays recommended And also new integer types. Christian: Downgrade Store/Restore FMU State to recommended Pierre: agree. You could backtrack. Remove Serialize/Deserialize FMU State"This should go into an optimization profile Pierre: besides "clocked ME", the dynamics controller profile is similar to the dynamics profile. Does it make sense to have a separate profile for this

chrbertsch avatar Feb 02 '23 15:02 chrbertsch