Estimate Density Map Peaks

How it fits

Typical backends

Caveats

• I/O contractThe number of returned peaks is capped at the second UInt64 input; when the map has fewer distinct local maxima than requested, fewer come out and there is no padding to the target.
• FallbackA requested count of zero short-circuits to an empty result without reading the density map, on every output arm.
• I/O contractPeak coordinates are sub-pixel doubles in the density-map coordinate frame (which matches the source-image resolution when the map is full size), so downstream visualisers can plot them directly.
• I/O contractOn the [Landmark] arm each peak's density value is carried as the landmark confidence; on the UInt64 arm only the count of found peaks is emitted.
• Hard constraintThe DensityMap input must be 2-D with shape (H, W) and a data length of exactly H times W; any other shape aborts mid-tick.
• Parameter interactionwindow_size is the neighbourhood radius used to suppress non-maximal points: lower it to separate closely-spaced targets, raise it to merge noisy clusters; a value of zero is rejected at startup.
• FallbackA connected local-maximum region whose total density weight is exactly zero is dropped as degenerate.
• CostThe pass is CPU-only and per-tick cost grows with the density-map area (H times W).