-
Notifications
You must be signed in to change notification settings - Fork 771
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ros2] Sensor noise not loaded in tests using ServerFixture #799
Comments
I see the errors even when just running Gazebo, both on the terminal and on the log file:
I see a couple differences in the output, I have:
And you have:
|
if you always see the error you're maybe testing with a world file that doesn't specify noise, yeah? |
Yeah I run the test world, just like in the beginning of the issue description, and that doesn't have noise:
|
bah, that was a very poorly worded description sorry. We spoke offline but for other readers, it should be: |
I didn't realise that the test is relying on a version of the world file copied to the build directory. I had modified the world file in the source directory to add noise. Rebuilding didn't trigger a re-copy, so it was still using the world file without noise. In summary, this was user error. Thanks for taking a look still @chapulina ! |
This world file specifies noise for an IMU sensor:
gazebo_ros_imu_sensor.world.txt
If it's loaded via the commandline with (updated from original post for clarity):
the following is output to
~/.gazebo/server-11345/default.log
(the sensor noise is applied):However, if the world file is loaded from a test using ServerFixture with
this->Load("worlds/gazebo_ros_imu_sensor.world", true);
, the log file has the following:The errors are from failed calls to
sensor->Noise()
in the plugin (https://github.com/ros-simulation/gazebo_ros_pkgs/pull/793/files#diff-43a08bb3c10236c3fea23e88cfcc1d68R81 ) since the noise does not appear to ever be set.good_imu_noise_from_cmdline.log
bad_imu_noise_from_test.log
The text was updated successfully, but these errors were encountered: