Detections Merge¶
Class: DetectionsMergeBlockV1
Source: inference.core.workflows.core_steps.transformations.detections_merge.v1.DetectionsMergeBlockV1
The DetectionsMerge
block combines multiple detections into a single bounding box that encompasses all input detections.
This is useful when you want to:
- Merge overlapping or nearby detections of the same object
- Create a single region that contains multiple detected objects
- Simplify multiple detections into one larger detection
The resulting detection will have:
- A bounding box that contains all input detections
- The classname of the merged detection is set to "merged_detection" by default, but can be customized via the class_name
parameter
- The confidence is set to the lowest confidence among all detections
Type identifier¶
Use the following identifier in step "type"
field: roboflow_core/detections_merge@v1
to add the block as
as step in your workflow.
Properties¶
Name | Type | Description | Refs |
---|---|---|---|
name |
str |
Enter a unique identifier for this step.. | ❌ |
class_name |
str |
The class name to assign to the merged detection.. | ❌ |
The Refs column marks possibility to parametrise the property with dynamic values available
in workflow
runtime. See Bindings for more info.
Available Connections¶
Compatible Blocks
Check what blocks you can connect to Detections Merge
in version v1
.
- inputs:
Segment Anything 2 Model
,Line Counter
,Keypoint Detection Model
,PTZ Tracking (ONVIF)
.md),Detections Stabilizer
,Byte Tracker
,Path Deviation
,Overlap Filter
,Gaze Detection
,VLM as Detector
,Object Detection Model
,Time in Zone
,Instance Segmentation Model
,Dynamic Zone
,Keypoint Detection Model
,Google Vision OCR
,Byte Tracker
,Detections Consensus
,Byte Tracker
,Detection Offset
,Detections Filter
,Time in Zone
,Object Detection Model
,Bounding Rectangle
,Detections Transformation
,Detections Classes Replacement
,YOLO-World Model
,Detections Merge
,Perspective Correction
,Moondream2
,Path Deviation
,Template Matching
,Instance Segmentation Model
,Velocity
,Detections Stitch
,VLM as Detector
,Dynamic Crop
- outputs:
Segment Anything 2 Model
,Stitch OCR Detections
,Line Counter
,Crop Visualization
,Line Counter
,Triangle Visualization
,Blur Visualization
,PTZ Tracking (ONVIF)
.md),Background Color Visualization
,Color Visualization
,Detections Stabilizer
,Corner Visualization
,Byte Tracker
,Path Deviation
,Icon Visualization
,Overlap Filter
,Pixelate Visualization
,Circle Visualization
,Model Comparison Visualization
,Time in Zone
,Byte Tracker
,Detections Consensus
,Roboflow Dataset Upload
,Byte Tracker
,Roboflow Dataset Upload
,Detection Offset
,Detections Filter
,Trace Visualization
,Roboflow Custom Metadata
,Dot Visualization
,Time in Zone
,Detections Transformation
,Bounding Box Visualization
,Detections Classes Replacement
,Ellipse Visualization
,Size Measurement
,Detections Merge
,Florence-2 Model
,Perspective Correction
,Florence-2 Model
,Path Deviation
,Model Monitoring Inference Aggregator
,Velocity
,Detections Stitch
,Label Visualization
,Distance Measurement
,Dynamic Crop
Input and Output Bindings¶
The available connections depend on its binding kinds. Check what binding kinds
Detections Merge
in version v1
has.
Bindings
-
input
predictions
(Union[object_detection_prediction
,instance_segmentation_prediction
,keypoint_detection_prediction
]): Object detection predictions to merge into a single bounding box..
-
output
predictions
(object_detection_prediction
): Prediction with detected bounding boxes in form of sv.Detections(...) object.
Example JSON definition of step Detections Merge
in version v1
{
"name": "<your_step_name_here>",
"type": "roboflow_core/detections_merge@v1",
"predictions": "$steps.object_detection_model.predictions",
"class_name": "<block_does_not_provide_example>"
}