Build anchors from averages, medians, ratios, and stride. Compare sizes, review fit, and download reports. Helpful visuals keep model tuning organized, faster, and practical.
Use dataset statistics, stride, scale multipliers, and aspect ratios to estimate anchor widths and heights for object detection training.
| Class | Avg Width | Avg Height | Median Width | Median Height | Typical Ratio | Suggested Scale |
|---|---|---|---|---|---|---|
| Pedestrian | 34 | 78 | 30 | 74 | 0.44 | 0.75 |
| Vehicle | 96 | 62 | 92 | 58 | 1.55 | 1.25 |
| Traffic Sign | 42 | 41 | 40 | 40 | 1.02 | 0.50 |
| Helmet | 28 | 25 | 26 | 24 | 1.12 | 0.50 |
1) Blended reference size
Reference width = Average width × (1 − blend weight) + Median width × blend weight
Reference height = Average height × (1 − blend weight) + Median height × blend weight
2) Base anchor size
Base size = max(feature stride, √(reference width × reference height) × coverage factor)
3) Anchor width and height
Anchor width = Base size × Scale × √(aspect ratio)
Anchor height = Base size × Scale ÷ √(aspect ratio)
4) Centered IoU check
IoU = Intersection area ÷ Union area, using same-center boxes. This helps compare candidate anchors with a validation object size.
It estimates candidate anchor widths and heights for detection models. It combines object statistics, stride, aspect ratios, and user-selected scales to create anchor options you can compare before training.
Averages reflect the overall dataset, while medians reduce the effect of outliers. Blending both gives a steadier reference size when your object distribution is skewed.
The coverage factor scales the base anchor size up or down. Higher values create larger anchors, which can help when you want more context around typical objects.
Stride links the anchor design to the feature map resolution. A very small anchor on a coarse feature map often performs poorly, so the formula prevents the base size from dropping below stride.
It measures overlap between a candidate anchor and a validation object size, assuming both boxes share the same center. It is a quick screening metric, not a full dataset evaluation.
Pixel output is easier for manual review. Normalized output helps when comparing anchor sizes across different image resolutions or documenting model settings in a resolution-independent way.
No. It is a planning and sanity-check tool. K-means or auto-anchor methods still provide stronger data-driven optimization when you need production-grade anchor selection.
It is useful during early model setup, dataset audits, anchor debugging, or when you want a faster manual starting point before heavier experiments.
Important Note: All the Calculators listed in this site are for educational purpose only and we do not guarentee the accuracy of results. Please do consult with other sources as well.