Patrick Täuber

Standard is not clear about the information flow of Clocks

4

Apparently it is common understanding that input Clocks are able to provide information to other input Clocks (of another FMU). This is not clear by reading the standard document. In...

Non-normative text states that importers can deactivate output clocks

2

In section [2.3.5. State: Event Mode](https://fmi-standard.org/docs/3.0.1/#EventMode) in the description of the fmi3SetClock function the following example is given as non-normative text: _[Rationale: a triggered [output Clock](https://fmi-standard.org/docs/3.0.1/#outputClock) c may depend on...

Handling of time-based Clocks with interval=0

5

In section [2.3.5. State: Event Mode](https://fmi-standard.org/docs/3.0.1/#EventMode) in the description of the fmi3SetClock function the following restriction is made for time-based clocks: "Only [time-based Clocks](https://fmi-standard.org/docs/3.0.1/#time-based-clock) must not be active for more...

Fixes #1916 Removes the contradicting statement that aperiodic Clocks are not allowed to be activated more than once per Event Mode.

According to the FMI 3.0 standard, in Event Mode fmi3Get{VariableType} computes f_event (s. [2.3.5. State: Event Mode](https://fmi-standard.org/docs/3.0.1/#EventMode)). When fmi3UpdateDiscreteStates() is called and f_event is already computed (i.e., fmi3Get{VariableType} was called...