hx_move_region — 2D halcon_ext op

• Data kinds: region → region

• Call: fullseye.apply(img, "hx_move_region", a=0.5, b=0.5) (the 2-D model is one image plus two scalar knobs a,b∈[0,1])

• HALCON equivalent: move_region (the HALCON reference is a useful guide to its meaning and parameters)

hx_move_region: input → output

*The figure is the actual output on a synthetic 128×128 input. Left: input, right: output. Point clouds are drawn as a top-down scatter (brightness = z), 1-D series as a line plot, volumes as the maximum-intensity projection along z, videos as the middle frame, complex images as magnitude; return values that are not pictures are shown as the values themselves.*

Sweeping knob a (0.1 / 0.5 / 0.9, the other knob at its default):

▸ hx_move_region: knob a sweep (docs site)

Sweeping knob b (0.1 / 0.5 / 0.9, the other knob at its default):

▸ hx_move_region: knob b sweep (docs site)

Stages (the ops that come before → this op, left to right):

▸ hx_move_region: stages (docs site)

On other images (synthetic scene / photo / coins. Top row: inputs, bottom row: their outputs. Knobs at default):

▸ hx_move_region: other inputs (docs site)

Usage

Translate a region (dy = a, dx = b, taken as offsets around zero).

Treats v > 0.5 as the region and returns a 0/1 float array shifted by dy = int((a - 0.5) * H) rows and dx = int((b - 0.5) * W) columns (no shift at a = b = 0.5; int truncates toward 0). The shift is done with np.roll.

Because of np.roll, the edges wrap around (a region running off one side reappears from the opposite side). HALCON's move_region drops what leaves the edge (clipping), so the behaviour differs for moves that touch the edge -- for the feature use of evolution ops, the design that keeps uniformity by wrapping is retained, and the difference is disclosed here.

Detailed usage guide

• gallery2d_halcon_ext family guide

References (sample data, literature)

• Sample-data catalog (download URLs / licences) — 2-D uses skimage.data (BSD/public domain) plus synthetic images; 3-D lists download URLs for real data sources (Stanford, PDS, …).

• Operator provenance and references — the sources of the research/methods this op family came from.

• The canonical algorithm (author, year) and its uses are named in the family usage guide above.

Try it in Studio

The program below has been verified to run (same input as the figure). In Studio's help this block becomes buttons that load and run it on the spot.

threshold 0.50 0.50
hx_move_region 0.50 0.50

▸ Load this pipeline  ·  Load & run

Runnable examples (verified samples that actually call this op)

• gallery2d_halcon_ext — py -3.11 examples/gallery2d_halcon_ext.py

Ops the type connects to (they accept region as input)

identity · reg_erode · reg_dilate · reg_open · reg_close · fill_holes · select_largest · remove_small

Same category (halcon_ext)

hx_gen_circle · hx_gen_ellipse · hx_gen_rectangle2 · hx_gen_checker_region · hx_gen_grid_region · hx_gabor · hx_fit_surface1 · hx_fit_surface2


*Provenance: ops.py — 2D operator registry. This per-op note is generated by tools/opdocs.py md (do not hand-edit).*

© 2026 Kazufumi Furuse — Fullseye operator documentation. Licensed under Apache-2.0.