Revert usage of tf listener node in favor of callback group#881
Open
Flova wants to merge 1 commit intoros2:rollingfrom
Open
Revert usage of tf listener node in favor of callback group#881Flova wants to merge 1 commit intoros2:rollingfrom
Flova wants to merge 1 commit intoros2:rollingfrom
Conversation
Signed-off-by: Florian Vahl <florian@flova.de>
Author
|
Friendly ping @clalancette |
Author
|
Are there any issues with this PR? @clalancette |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reverts the changes from #551 as ros2/rclcpp#1218 is now merged.
The parallelism and performance should be unaffected because tf uses a callback group which is spon by its own executor instance for the tf topics. See PR ros2/geometry2#442 for the addition of this behavior.
This PR reduces the overhead from having more nodes. In addition to that, it also reduces the number of nodes in the rqt node graph and makes the subscriptions more visible, as the subscription can be directly associated with the parent node which is otherwise not the case (only something like tf_listener_xxxxx is shown, with no indication regarding the real node that creates the tf listener).