Add option to bind mobility model ticks to system clock #555
+44
−4
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Adds parameters 'use_timed_model_mob' and 'timed_model_mob_tick' to mobility model code. When enabled, these will cause mobility ticks to only occur every 'timed_model_mob_tick' seconds as long as the expected number of ticks for this time interval has occurred.
The current behavior does provide a 0.5s sleep time without the plot but does not prevent error from accumulating over time- over 30s, we can see a 100ms divergence from the expected timing of a tick develop when this sleep time is included. This likely varies from system to system, but this in turn means that reproducibility between systems is fraught. This also allows the end user to control this sleep interval and visualize the behavior as it occurs without the plot more easily.