You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When clocks diverge too much, it results in this error:
Cannot schedule message (inet::ClockEvent)ProductionTimer to the past, t=0.0469998 -- in module (inet::queueing::ActivePacketSource) ClockDriftShowcase.source2.app[0].source (id=208), at t=0.047s, event #142502
For reproduction: run OutOfBandSynchronizationRandomDrift config
The clock time of a SettableClock is changed (e.g. from 100 -> 200) such that there are clock events which are overdue. In the above configuration overdue events are to be executed, but that means they have to be rescheduled for the current simulation time. Unfortunately, it's not possible to execute them right away while the clock is being set from 100 to 200, and rescheduling them for execution is also wrong because the clock will be already set to 200, so an event at clock time 150 will execute at 200.
The above exception comes when the completely unrelated drifting oscillator changes its drift rate (by a random walk process) and the clock wants to reschedule all to be executed events according to the new drift rate. The clock suddenly finds an event that needs to be rescheduled, which has an arrival clock time in the past. This should not normally happen, but the event was overdue at the last time the clock was set (e.g. moved forward from 100 to 200), and the event was not executed at that moment.
I still need to investigate this further to figure out what is the correct solution.
When clocks diverge too much, it results in this error:
Cannot schedule message (inet::ClockEvent)ProductionTimer to the past, t=0.0469998 -- in module (inet::queueing::ActivePacketSource) ClockDriftShowcase.source2.app[0].source (id=208), at t=0.047s, event #142502
For reproduction: run
OutOfBandSynchronizationRandomDrift
configNED:
INI:
The text was updated successfully, but these errors were encountered: