Skip to content
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

Open
jvonhacht opened this issue Mar 2, 2021 · 2 comments
Open

[Question] Stop advertising specific topics #679

jvonhacht opened this issue Mar 2, 2021 · 2 comments

Comments

@jvonhacht
Copy link

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:

[ZED][Grab] WARNING: Depth or confidence map view asked but depth map not computed (MODE_NONE)
[ZED][Grab] WARNING: Depth or confidence map view asked but depth map not computed (MODE_NONE)

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

@Myzhar
Copy link
Member

Myzhar commented Mar 2, 2021

Hi @JohanKJIP
this is indeed wrong behavior. When setting depth mode to NONE we should not advertise all the topics related to depth calculation.
I suggest you modify the code to disable depth advertising and to be able to perform your task quickly, meanwhile we will schedule this modification for a future release.
It's an enhancement that requires many modifications and checks, so it requires a bit of time before it will be released.

@jvonhacht
Copy link
Author

Thanks for the quick reply! That is understandable, I will modify the code for now 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants