-
Notifications
You must be signed in to change notification settings - Fork 773
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
Parameter to disable ROS network interaction from/to Gazebo #585
Conversation
advertiseServices(); | ||
|
||
// Manage clock for simulated ros time | ||
pub_clock_ = nh_->advertise<rosgraph_msgs::Clock>("/clock",10); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/clock is already advertised within advertiseServices(), perhaps it should be removed there.
<arg name="gui" value="false"/> | ||
<arg name="headless" value="false"/> | ||
<arg name="debug" value="false"/> | ||
<arg name="enable_ros_network" value="true" /> |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Perhaps this argument should be excluded entirely in this test to ensure the default behavior is enabled.
Bump to trigger CI, good to merge if no regressions |
out of date, probably can be left out |
The PR implements a ROS parameter named
enable_ros_network
that allows to disable all the gazebo topics (except /clock) and services that are created from thegazebo_ros
package. This is useful in situation where the interaction from user with the gazebo simulator should be limited or blocked.To keep backwards compatibility, by default, the behaviour is to enable all topics and services if the parameter is not present so current code should not experiment any difference at all.
I've added a couple of tests based on the
ros_api_checker
that the OSRF developed during the times of the Virtual Robotics Challenge. It checks all the ROS topics and services in runtime to check if they are exactly the same that is described in the .yaml files available in this PR.