Patrick Täuber

Any new insights here?

How would you propose to fix that? I think it makes sense to allow interval=0 for aperiodic and triggered clocks and to disallow it for periodic clocks.

That there are different kinds of input clocks (one kind functioning as a clock source and the other only as a consumer) with the connection rules you mentioned above is...

I think whether and when it is allowed to call fmi3GetInterval* is already precisely defined. > So interestingly, for fixed/tunable you can only call fmi3GetInterval/fmi3GetShift if no interval is provided...