Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Handling triggered clocks (triggered time-events) #589
Triggered clocks tick due to state, step, and time events.
Note that, unlike inferred clocks where the simulator is allowed to perform a SetClock() to indicate to the FMU that an inferred clock has ticked, for triggered clocks, this is not possible.
In order to avoid such numerical errors or using error tolerances in time event comparison, the simulator should be allowed to do SetClock() on triggered clocks too.
Am I missing something? In any case, we would need a solution to get rid of time-event comparison inside the FMU to detect and tick a triggered clock.