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.
PR Details
Description
If simulation mode is on, carma-platform will publish automatic driver status messages in ROS2 because ros1_bridge is dropping messages which is timing out the platform depending on the computer's performance.
There should be another PR in carma-carla-integration tool to disable the previous ROS1 node. Supporting PR:
usdot-fhwa-stol/carma-carla-integration#66
Related GitHub Issue
Partially fixes this issue:
#2186
(full fix would be to also port the rosbag mock_drivers, this node doesn't mock rosbags)
Related Jira Key
TODO
Motivation and Context
Integration testing VRU use case - platform is timing out due toe driver status messages being dropped over the ros1_bridge depending on the PCs
How Has This Been Tested?
Simulation PC 1
Types of changes
Checklist: