-
Notifications
You must be signed in to change notification settings - Fork 391
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
[Question] Stop advertising specific topics #679
Comments
Hi @JohanKJIP |
Thanks for the quick reply! That is understandable, I will modify the code for now 😄 |
@Myzhar curious if advertising only select topics is still on your roadmap sometime? |
No modifications are scheduled for the ZED ROS Wrapper. Our current focus is on the ZED ROS2 Wrapper because ROS 1 will soon reach its end of life. If you're interested, feel free to submit a Pull Request with new features, which will be reviewed and potentially merged. |
Oh, my bad. I keep mixing up Is this a feature that's possibly planned for |
It's already available in the ROS 2 wrapper if you disable the depth processing |
Question: Is it possible to stop advertising specific topics in any of the config files? (in particular the depth topics)
We are using the ZED for a robotics task and don't want to perform depth calculations since we don't need it and it slows down the system. As I understand it, the calculations are not performed and published as long as we don't subscribe to the depth topics. However, the problem is that we need to record a rosbag with the -a flag and with this, the rosbag subscribes to those topics and the calculations are performed anyways.
The first attempt to solve the issue was to disable the depth calculations by setting the depth mode to 0 (MODE_NONE) in the parameter config file. With this, the zed node dies as soon as the rosbag recording is started:
The last resort is to edit the source in this file on line 400 and below to disable the advertising. This is not an optimal solution, surely there must be a better way that I am missing.
Thanks
The text was updated successfully, but these errors were encountered: