fullseye

HALCON operator coverage (measured vs the real reference)

Source: https://www.mvtec.com/doc/halcon/2605/en/ (version 2605). Ground truth: 2313 operators across 30 top-level chapters (218 TOC pages), mined by halcon_scrape.py.

imgevolve maps to 981 / 2313 HALCON operators (42.4%) via Op.halcon, from 860 registry ops.

One imgevolve op claims one nearest HALCON operator, so coverage counts distinct real operators with an analogue. This number is grounded in the scraped reference, not memory; grow it by adding operator families to the registry (each new Op.halcon that names a real operator lifts coverage).

Per-chapter coverage (ranked by gap)

chapter covered total gap
Graphics 9 174 165
Tuple 0 165 165
System 0 141 141
Classification 0 99 99
OCR 0 96 96
Legacy 16 110 94
Deep Learning 4 88 84
Matching 38 96 58
File 0 53 53
3D Matching 15 59 44
Inspection 12 55 43
Develop 0 37 37
Control 0 34 34
Calibration 35 68 33
3D Reconstruction 50 76 26
Identification 1 27 26
Image Source 0 25 25
Image 88 110 22
2D Metrology 10 32 22
Tools 90 108 18
Object 1 16 15
Transformations 104 118 14
Matrix 46 57 11
3D Object Model 40 51 11
Filters 186 196 10
XLD 88 97 9
1D Measuring 11 20 9
Segmentation 48 53 5
Morphology 42 44 2
Regions 105 106 1

Build targets — biggest gaps first (sample uncovered operators)

Version awareness (HALCON’s op set changes between releases)

Operator counts per scraped release: v12=2147, v13=2176, v2311=2381, v2411=2387, v2505=2411, v2605=2313 (union 2466). Coverage above is vs the primary scrape; the classification below is honest about which claimed Op.halcon names are stable vs release-specific.

Honest reading