Parser generator differentiates YOLO subtypes#283
Open
aljazkonec1 wants to merge 4 commits intomainfrom
Open
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
This PR enhances the parser generator to properly differentiate between YOLO model subtypes and leverage native DepthAI detection parsers where supported, instead of defaulting to YoloExtendedParser for all YOLO models. The implementation adds special handling for YOLO segmentation models on RVC2 devices, which must run parser logic on the host.
Changes:
- Added logic to check YOLO subtypes against a list of models supported by
dai.DetectionParser - Implemented RVC2-specific handling for segmentation models to force host-side parsing
- Added logging to inform users when segmentation mask processing occurs on the host
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Contributor
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 1 out of 1 changed files in this pull request and generated no new comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
klemen1999
reviewed
Feb 18, 2026
This file contains hidden or 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
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.
Purpose
Current implementation of parser generator preffers YoloExtendedParser for all YOLO models even though most models are now directly supported in
dai.DetectionParser. One caveat is in the case of YOLO segmentation on RVC2 where dai only supports running the parser on the host side.Specification
None / not applicable
Dependencies & Potential Impact
None / not applicable
Deployment Plan
None / not applicable
Testing & Validation
Tested on oak-examples generic example with the following models (both on RVC2 and RVC4):
Other models (yolo-p, yolo-world, yolo-e) crash their respective examples as oak-examples need to be updated to accmodate the change in segmentation mask.