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

Port to ROS2 #21

Open
tonynajjar opened this issue May 31, 2022 · 3 comments
Open

Port to ROS2 #21

tonynajjar opened this issue May 31, 2022 · 3 comments
Labels
help wanted Extra attention is needed

Comments

@tonynajjar
Copy link

tonynajjar commented May 31, 2022

Hey @MichaelGrupp :)

I'd like to use this in ROS2, any interest in porting this to ROS2? I'm happy to help with some guidance from your side

@tonynajjar tonynajjar closed this as not planned Won't fix, can't repro, duplicate, stale Jul 27, 2022
@MichaelGrupp
Copy link
Member

MichaelGrupp commented Jul 27, 2022

Hi Tony, sorry for the late reply. Porting to ROS2 would be nice, however at the moment this would need to be done mainly with external contribution because I don't plan to do this myself in the next time. What I could do is to set up a ros2 branch against which you (or other persons) can create PRs for the port and I can assist in PR reviews.

I cannot help with the implementation details for ROS2 at the moment, but to me the work to be done looks like:

  • port pure C++ implementation & test (this should be relatively easy to do I think)
  • port Python bindings (here there could be some things that need to be taken care of, e.g. the internal node handle that we have in the ROS1 version)
  • port Python tests
  • create a CI job including Dockerfile
  • adapt README for ROS2

@MichaelGrupp MichaelGrupp reopened this Jul 27, 2022
@MichaelGrupp MichaelGrupp added the help wanted Extra attention is needed label Jul 27, 2022
@MichaelGrupp
Copy link
Member

Also, in the README we have this here as a motivation for ROS1 explaining why the existing TF2 BufferServer is bad:

The idea is great, but it can scale badly with the number of clients and requests. This is due to the broadcast nature of the ROS action protocol, where each client receives status update callbacks of the currently active goals.

Are ROS2 actions also implemented in such an ugly way? If they are not, this would mean that it would be worth to do some benchmarking of the performance of the TF2 BufferServer in ROS2, maybe it's not so bad anymore?

@tonynajjar
Copy link
Author

tonynajjar commented Dec 9, 2022

Sorry for the long wait, we threw back this in the backlog until now.

Are ROS2 actions also implemented in such an ugly way?

I'm not 100% sure of the internals but my observation is that in ROS2 all action clients to a certain server subscribe to the status topic yes.

This PR might interest you ros2/geometry2#573. A service is probably the right way to go long-term, even with this PR but what is the reason you didn't directly go for implementing a service in the existing buffer server as suggested here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

2 participants