Simulation time and wall time
Separate modeled time from the clock used to schedule a real process.
Research note · November 14, 2026Research question
What happens when simulation time pauses, accelerates or moves backward?
Method
- Record which clock every component uses for deadlines, timestamps and integration. A wall-clock timeout and a simulated duration should have different labels.
- Pause a controlled simulation while the external process continues. Inspect whether commands accumulate, expire or are applied immediately when the simulation resumes.
- Test a backward time jump caused by resetting the scene. Reset or explicitly invalidate time-dependent buffers and preserve the event in the run history.
Records to retain
- Clock source per component
- Pause and reset events
- Command timestamps
- Deadline and buffering behavior
Source basis
The ROS time design addresses simulated time, time jumps and the distinction from system and steady clocks. A component that assumes time always advances can behave incorrectly during replay or simulation reset.
Interpretation & limits
A simulated clock does not make a real device rewindable. This is a clock-boundary test, not a promise of deterministic replay across hardware.
Next experiments
- Test pause and reset with one buffered input stream.
- Document which deadlines must remain tied to elapsed real time.
References
Technical reference
Implementation details supporting this note, drawn directly from the maintained documentation. These are technical references, not additional papers or new experimental results. Expand a topic to inspect its method, fields and limits.