Clarify restrictions on "intermediateUpdate" about fmi-standard HOT 3 CLOSED

"structuralParameters" & "calculatedParameters" should not be marked with intermediateUpdate = true; to my understanding this is already clear (but could be made more explicit): in the definition of "requiredIntermediateVariables" (https://fmi-standard.org/docs/main/#requiredIntermediateVariables) it is already stated that "For Co-Simulation, these intermediate variables must be continuous-time variables.", and as listed in https://fmi-standard.org/docs/main/#table-allowed-variability-causality-combinations, this excludes structural and calculated parameters.
(btw. "For Co-Simulation ... " is misleading, as intermediateUpate is only used in CS. Should we change this?)

Regarding Clock variables: As they must not have the intermediateUpdate attribute, they cannot be part of "requiredIntermediateVariables" and thus cannot be set. I do no know what to clarify here.

from fmi-standard.

Thanks for clarifying the more explicit restriction with the MR.

As for the Clock variables, this might be more of a language consistency concern. "...must not have [...] attribute ..." can be read as "The mere existence of this attribute is erroneous, irregardless of the value". This is particularly odd, since there is a default value.

Compare:

1. "Type definitions without unit must not have a unit attribute."
2. "A structural parameter must not have a element"
3. For the variable with causality = independent, the attribute initial must not be provided, because its start value is set with the startTime parameter of fmi3EnterInitializationMode.

How about "Variables of type Clock must not be marked with intermediateUpdate = true"?

from fmi-standard.

Hm.
As in the FMI 3.0. release the sentence "Variables of type <> must not have the <> attribute." is already in, Clocks may really not have this attribute, so it is not only about the value.

from fmi-standard.