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
This PR reduces the image dimensions specified in the mono_camera.launch file. When using the previous image dimensions, the frequency at which images were forwarded to the carma system reached low enough rates (as measured by
rostopic hz /hardware_interface/camera/image_raw
) that the carma system would shutdown due to a 'camera failed' error. By reducing the image dimensions, the frequency at which images are received remains at a high enough rate that the error does not occur.Due to these updated image dimensions, the camera and lidar on carma vehicles will need to be recalibrated. This is captured in Issue #1241: Recalibrate camera and lidar due to updated image dimensions in avt_vimba_driver's mono_camera.launch file
Related Issue
Motivation and Context
By reducing the image dimensions, the frequency at which images are received by the carma system remains at a high enough rate that a 'camera failed' issue does not occur.
How Has This Been Tested?
This has been tested on the Blue Lexus.
Types of changes
Checklist:
CARMA Contributing Guide