Initialization of the HALCON system.
The operator reset_obj_db initializes the HALCON system. With this procedure the four relations (grayvalue data, region data, iconic objects and object tuplets) which are necessary for image processing with HALCON will be installed (see also count_relation). In case the relations already exist, all tuplets in the relations will be deallocated!
The parameters DefaultImageWidth and DefaultImageHeight provide the initial values for the global maximum image size. If the first created object is an image, (e.g. read_image), the set values will be overruled in Standard-HALCON by the size of this picture. Instead of this, in Parallel HALCON the set values will only be changed, if they are smaller than the size of the created object. If on the other hand the first object to be created is a region, both in Standard- and in Parallel HALCON the values will only be adjusted in case the new image is larger than the set values. This is not only the case for the first image which is created or read: the global image size will always be enlarged, if larger images are created.
The global image size is of consequence for the opening of windows (open_window) and the clipping of regions. Whenever the clip mode is activated, regions will be clipped according to the global image size (set_system('clip_region','true')). This can lead to problems if images of various sizes are used. In this case only the fact that a region is smaller or of the same size as the largest image can be guaranteed.
The parameter DefaultChannels returns the most frequent number of channels of an image object. This value can be set to 0 if for the most part regions are used. If more channels than those having been set at the initialization are necessary for one image, the number will be enlarged dynamically for this image. If less channels than those having been set at the initialization are necessary for the image, the superfluous channels will be set as undefined. For the user this will seem as if they were non existent, however, memory is allocated unnecessarily.
The parameter values can be queried using the operator get_system.
If the operator reset_obj_db is not called at the beginning of a HALCON session, HALCON will be initialized automatically by the operator reset_obj_db(128,128,0). In case the operator reset_obj_db is called again, all image objects in the database will be deallocated.
|
DefaultImageWidth (input_control) |
integer -> integer |
| Default image width (in pixels). | |
| Default value: 128 | |
| Suggested values: 64, 128, 256, 512, 525, 1024 | |
|
DefaultImageHeight (input_control) |
integer -> integer |
| Default image height (in pixels). | |
| Default value: 128 | |
| Suggested values: 64, 128, 256, 512, 768, 1024 | |
|
DefaultChannels (input_control) |
integer -> integer |
| Usual number of channels by which the system constant 'max_channels' is limited. | |
| Default value: 0 | |
| Suggested values: 0, 1, 2, 3, 4, 5, 6, 7 | |
The operator reset_obj_db returns the value 2 (H_MSG_TRUE) if the parameter values are correct. Otherwise an exception will be raised.
reset_obj_db is reentrant and processed without parallelization.
get_channel_info, count_relation
Foundation
