feat/core: BoT-SORT block#2349
Merged
PawelPeczek-Roboflow merged 3 commits intoMay 15, 2026
Merged
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
PawelPeczek-Roboflow
approved these changes
May 15, 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.
What does this PR do?
Following Trackers 2.4.0 release, where we added BoT-SORT tracker (our new best one), we are adding it to workflows!
It is the first and only so far that takes an image as input along to detections in order to compensate camera motion between frames!
Type of Change
Testing
Added tests following the other trackers and tried custom workflow:
{ "version": "1.0", "inputs": [ { "type": "WorkflowImage", "name": "image" } ], "steps": [ { "type": "ObjectDetectionModel", "name": "model", "image": "$inputs.image", "model_id": "yolov8n-640", "confidence": 0.25, "class_filter": ["person"] }, { "type": "roboflow_core/trackers_botsort@v1", "name": "tracker", "image": "$inputs.image", "detections": "$steps.model.predictions", "minimum_consecutive_frames": 1, "enable_cmc": true, "cmc_method": "sparseOptFlow", "cmc_downscale": 2 }, { "type": "roboflow_core/bounding_box_visualization@v1", "name": "boxes", "image": "$inputs.image", "predictions": "$steps.tracker.tracked_detections", "color_axis": "TRACK", "thickness": 2 }, { "type": "roboflow_core/label_visualization@v1", "name": "labels", "image": "$steps.boxes.image", "predictions": "$steps.tracker.tracked_detections", "text": "Tracker Id", "color_axis": "TRACK" }, { "type": "roboflow_core/trace_visualization@v1", "name": "traces", "image": "$steps.labels.image", "predictions": "$steps.tracker.tracked_detections", "color_axis": "TRACK" } ], "outputs": [ { "type": "JsonField", "name": "preview", "selector": "$steps.traces.image" } ] }Had problems with the docker server so couldn't test the UI in local.
We now generate warnings if cmc is enabled and frame is not passed, or viceversa, when the tracker doesn't use frame and it is passed.
Checklist