Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify when to use Scheduled Execution #1979

Merged
merged 2 commits into from
Oct 2, 2024
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/1___overview.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -119,6 +119,7 @@ image::images/co-simulation-data-flow.svg[width=40%, align="center"]
The Scheduled Execution interface exposes individual <<model-partition, model partitions>>.
A scheduler provided by the <<importer>> can control the execution of each model partition separately.
In some ways the Scheduled Execution interface has similarities to the Model Exchange interface: the first externalizes a scheduling algorithm usually found in a controller algorithm (see <<fmi-for-scheduled-execution>>) and the second interface externalizes the ODE/DAE solver.
_[See also https://modelica.github.io/fmi-guides/main/fmi-guide/#_use_cases_for_scheduled_execution[Use-cases for Scheduled Execution] in the FMI 3.0 Implementers' Guide.]_

.Schematic view of data flow between user, the scheduler of the importer and model partitions of the FMU for Scheduled Execution
[#figure-scheduled-execution-data-flow]
Expand Down