Add reentrant callback group to lidar, cameras and airsim control timers #4559
Conversation
This file contains 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
…ers, use multithreaded executor for spinning
|
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fixes #4428
About
This will fix the issue by using a multithreaded executor and adding a reentrant callback group to lidar, cameras, and airsim control timers. That way they can all execute in parallel and not block each other. Also removed unreachable code in airsim_node.cpp.
How Has This Been Tested?
Added a settings file with multiple cameras and a lidar, did a /airsim_node/local_position_goal service call.
Screenshots (if appropriate):