Closed paulbourelly999 closed 7 months ago
CARMA Ambassador was sending timestep updates 100 ms ahead of time. This is because the CARMA Ambassador was using the value for the next time step requested instead of the value of the current time step for time sync messages.
CDAR-764
Fix CARMA Time sync
CDASim Deployment
Kudos, no new issues were introduced!
0 New issues 0 Security Hotspots 0.0% Coverage on New Code 0.0% Duplication on New Code
See analysis details on SonarCloud
PR Details
Description
CARMA Ambassador was sending timestep updates 100 ms ahead of time. This is because the CARMA Ambassador was using the value for the next time step requested instead of the value of the current time step for time sync messages.
Related GitHub Issue
Related Jira Key
CDAR-764
Motivation and Context
Fix CARMA Time sync
How Has This Been Tested?
CDASim Deployment
Types of changes
Checklist: