[noetic-devel] support multiple encoding #29
Merged
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
Alpaca-zip
changed the title
Closed
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.
Fixed using
imgmsg_to_cv2()to pass the image inbgr8encoding to the track function.(related issue: Ensure BGR Encoding Compliance for Images Passed to track Function #16 )
The following encodings should be converted to
bgr8encoding and passed correctly to the track function.mono8: CV_8UC1, grayscale imagemono16: CV_16UC1, 16-bit grayscale imagebgr8: CV_8UC3, color image with blue-green-red color orderrgb8: CV_8UC3, color image with red-green-blue color orderbgra8: CV_8UC4, BGR color image with an alpha channelrgba8: CV_8UC4, RGB color image with an alpha channelChanges to the appearance of the README. In particular, added a description of support for YOLOv8, YOLOv8-seg, and YOLOv8-pose.