feat: ✨ yolov8-obb support and OrientedBoxAnnotator added for obb #770
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.
Description
This pull request introduces two significant features:
YOLOv8 Oriented Bounding Box (OBB) Support: This feature extends the capabilities of the YOLOv8 model to detect objects in images and provide oriented bounding boxes as output. This is particularly useful in scenarios where the orientation of the object matters, such as detecting vehicles or buildings from aerial images. The support for OBB allows the model to provide more precise and detailed information about the detected objects.
OrientedBoxAnnotator: This new class provides functionality for annotating images with oriented bounding boxes. This can be used to visually verify the output of the YOLOv8 model with OBB support or to create new training data. The OrientedBoxAnnotator makes it easy to draw oriented bounding boxes on images, which can be a complex task due to the need to handle the orientation of the boxes.
These features enhance the capabilities of the library in handling object detection tasks where object orientation is important. They also provide users with easy-to-use tools for working with oriented bounding boxes, both in terms of model output and data annotation.
List any dependencies that are required for this change.
Type of change
Please delete options that are not relevant.
How has this change been tested, please provide a testcase or example of how you tested the change?
Collab link: https://colab.research.google.com/drive/1DzXhkECpLbeWgGwDMsaY4h8pUzsfsFsE?usp=sharing
YOUR_ANSWER
Any specific deployment considerations
For example, documentation changes, usability, usage/costs, secrets, etc.
Docs
Resolve #749
Resolve #757