Clarify when to use Scheduled Execution #1979
Conversation
| @@ -124,6 +124,9 @@ In some ways the Scheduled Execution interface has similarities to the Model Exc | |||
| [#figure-scheduled-execution-data-flow] | |||
| image::images/scheduled-execution-data-flow.svg[width=40%, align="center"] | |||
|
|
|||
| _[An external scheduler is only required if the importer needs direct control over the tasks, e.g. to avoid overruns in a real-time application. | |||
There was a problem hiding this comment.
I don't like the "is only required" because this is not relevant perspective. Better "An external scheduler allows to control scheduling of tasks and thus model partitions. Such an environment e.g. is required to execute real-time simulations."
If you really need to reference overruns I suggest "Only in a real-time execution overruns can occur and thus can be stressed." Actually mentioning preemption and priorities would be just as relevant to mention. So I rather suggest not to mention any since it is explained in more detail in the SE section.
| @@ -124,6 +124,9 @@ In some ways the Scheduled Execution interface has similarities to the Model Exc | |||
| [#figure-scheduled-execution-data-flow] | |||
| image::images/scheduled-execution-data-flow.svg[width=40%, align="center"] | |||
|
|
|||
| _[An external scheduler is only required if the importer needs direct control over the tasks, e.g. to avoid overruns in a real-time application. | |||
| To synchronize events between the importer and across FMUs, <<Clock, Clocks>> should be used that are available in all interface types.]_ | |||
There was a problem hiding this comment.
" The FMU provides model partitions defined by clocks in the FMU interface description. This way the importer can allow to configure the scheduling of each model partition, e.g. it enables to synchronize the execution across FMUs."
fixes #1948