Operator Reference

concat_objconcat_objConcatObjConcatObjconcat_obj (Operator)

concat_objconcat_objConcatObjConcatObjconcat_obj — Concatenate two iconic object tuples.

Signature

concat_obj(Objects1, Objects2 : ObjectsConcat : : )

Description

concat_objconcat_objConcatObjConcatObjconcat_obj concatenates the two tuples of iconic objects Objects1Objects1Objects1objects1objects_1 and Objects2Objects2Objects2objects2objects_2 into a new tuple of iconic objects ObjectsConcatObjectsConcatObjectsConcatobjectsConcatobjects_concat. Hence, this tuple contains all the iconic objects of the two input tuples:

ObjectsConcatObjectsConcatObjectsConcatobjectsConcatobjects_concat = [Objects1Objects1Objects1objects1objects_1,Objects2Objects2Objects2objects2objects_2]

In ObjectsConcatObjectsConcatObjectsConcatobjectsConcatobjects_concat, the objects of Objects1Objects1Objects1objects1objects_1 are stored first, followed by the objects of Objects2Objects2Objects2objects2objects_2, i.e., the order of the objects is preserved. Note that only references to the corresponding images and regions are stored in ObjectsConcatObjectsConcatObjectsConcatobjectsConcatobjects_concat, i.e., no new memory is allocated. Furthermore, this means that modifications of input images, e.g., with set_grayvalset_grayvalSetGrayvalSetGrayvalset_grayval, overpaint_grayoverpaint_grayOverpaintGrayOverpaintGrayoverpaint_gray, or overpaint_regionoverpaint_regionOverpaintRegionOverpaintRegionoverpaint_region directly affect the images of the output tuple ObjectsConcatObjectsConcatObjectsConcatobjectsConcatobjects_concat and vice versa.

concat_objconcat_objConcatObjConcatObjconcat_obj should not be confused with union1union1Union1Union1union1 or union2union2Union2Union2union2, in which regions are merged, i.e., in which the number of objects is modified.

concat_objconcat_objConcatObjConcatObjconcat_obj can be used to concatenate objects of different image object types (e.g., images and XLD contours) into a single object. This is only recommended if it is necessary to accumulate in a single object variable, for example, the results of an image processing sequence. It should be noted that the only operators that can handle such object tuples of mixed type are concat_objconcat_objConcatObjConcatObjconcat_obj, copy_objcopy_objCopyObjCopyObjcopy_obj, select_objselect_objSelectObjSelectObjselect_obj, and disp_objdisp_objDispObjDispObjdisp_obj.

For a short description of the iconic objects that are available in HALCON see the introduction of chapter Object.

Execution Information

Supports objects on compute devices.
Multithreading type: reentrant (runs in parallel with non-exclusive operators).
Multithreading scope: global (may be called from any thread).
Processed without parallelization.

Parameters

Objects1Objects1Objects1objects1objects_1 (input_object) object(-array) → object

Object tuple 1.

Objects2Objects2Objects2objects2objects_2 (input_object) object(-array) → object

Object tuple 2.

ObjectsConcatObjectsConcatObjectsConcatobjectsConcatobjects_concat (output_object) object-array → object

Concatenated objects.

Example (C)

/* generate a tuple of a circle and a rectangle */

gen_circle(&Circle,200.0,400.0,23.0);
gen_rectangle1(&Rectangle,23.0,44.0,203.0,201.0);
concat_obj(Circle,Rectangle,&CircleAndRectangle);
disp_region(CircleAndRectangle,WindowHandle);

Complexity

Runtime complexity: O(|Objects1Objects1Objects1objects1objects_1| + |Objects2Objects2Objects2objects2objects_2|);

Memory complexity of the result objects: O(|Objects1Objects1Objects1objects1objects_1| + |Objects2Objects2Objects2objects2objects_2|)

Result

concat_objconcat_objConcatObjConcatObjconcat_obj returns 2 ( H_MSG_TRUE) if all objects are contained in the HALCON database. If the input is empty the behavior can be set via set_system(::'no_object_result',<Result>:)set_system("no_object_result",<Result>)SetSystem("no_object_result",<Result>)SetSystem("no_object_result",<Result>)set_system("no_object_result",<Result>). If necessary, an exception is raised.

Module

Foundation

Operators