feat(api): accept a caller-supplied bbox to skip YOLO detection#46
Draft
MateoLostanlen wants to merge 3 commits into
Draft
feat(api): accept a caller-supplied bbox to skip YOLO detection#46MateoLostanlen wants to merge 3 commits into
MateoLostanlen wants to merge 3 commits into
Conversation
4 tasks
Collaborator
|
Implementation in #47 |
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
2 participants
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.
/predict; today the API re-runs its own YOLO over every frame, computing the same thing twice. This adds optionalbbox_xyxyn/bbox_confidencetoPOST /predict: the supplied box is taken as the detection for every frame, building one full-length tube and skipping the detector entirely for faster inference.predict(frame_detections=...)injection seam via a new puremake_forced_detections()core helper; no second inference path. The context margin (context_factor) is still applied server-side, so callers pass the tight detection box.roi_xyxyn(400); the detection cache is bypassed so synthetic boxes never pollute it.docs/specs/2026-06-11-api-forced-bbox-design.md.