Hi,
I noticed that floating-point precision sometimes affects sensor readings. I am using CARLA 0.9.10.1. Specifically, in the sensor.speedometer configuration
|
elif type_ == 'sensor.speedometer': |
I encountered an issue when setting the simulation FPS to 25 Hz. The time difference calculated by GameTime.get_time() in the following codes
|
if current_time - latest_time > (1 / self._reading_frequency) \ |
is:
current_time - latest_time = 0.03999999910593033
However, the expected reading interval is:
1 / self._reading_frequency = 0.04
This slight mismatch (due to > comparison) results in a SensorReceivedNoData error on the speedometer sensor.
Have you encountered this issue before? Is this considered expected behavior due to floating-point precision limits?
Thank you!
Hi,
I noticed that floating-point precision sometimes affects sensor readings. I am using CARLA 0.9.10.1. Specifically, in the
sensor.speedometerconfigurationleaderboard/leaderboard/autoagents/agent_wrapper.py
Line 151 in a87a341
I encountered an issue when setting the simulation FPS to 25 Hz. The time difference calculated by
GameTime.get_time()in the following codesleaderboard/leaderboard/envs/sensor_interface.py
Line 70 in a87a341
However, the expected reading interval is:
This slight mismatch (due to
>comparison) results in aSensorReceivedNoDataerror on the speedometer sensor.Have you encountered this issue before? Is this considered expected behavior due to floating-point precision limits?
Thank you!