These problems have been fixed. HDevelop procedures that generate an empty tuple sometimes did not behave as expected when executed JIT-compiled. Instead of generating an empty tuple, a tuple with one element was created. The execution of JIT-compiled procedures led to a memory leak if a switch statement had an expression as argument. On Linux systems, HDevelop sometimes crashed when the execution of long running operators was cancelled by moving the program counter or editing the program.
HDevelop operators with control output parameters, e. Occasionally, the error "negative width of area or 0 " was shown while zooming or moving the image in the Graphics Window.
Stopping JIT-compiled procedure execution via user interaction, e. When trying to execute a procedure JIT-compiled in parallel, the same JIT-compiler information or warning appeared multiple times in the output console. HDevelop programs involving try - catch blocks sometimes caused HDevelop to freeze. The auto completion always added a comma in the parameter list of a one-parameter function. The line profile showed unexpected behavior.
In particular, the y-size for the line profile was based on the current profile, so that the axis scaling changed when moving the ROI around. Now, the size for the line is based on the current image. While this had no impact on the general decoding performance, for print quality inspection this could have led to significantly varying quality grades for relatively similar images.
The example bottlet. If the cameras were defined in the opposite order than originally defined in the example program, the definition of the area to be rectified was broken. It stated that the slant angle is the angle between the object plane, which lies orthogonal to the optical axis of the camera, and the direction of the illumination.
Instead, the slant angle is the angle between the optical axis of the camera and the direction of the illumination. In this case, the model region did not fit the model image, which resulted in an incomplete model. Furthermore, in this case the program later tried to read the variable MPInCamPoseMapping, which was not instantiated. This caused a program exception. Additionally, the names of some parameters and the visualization have been improved.
The HDevelop language interfaces converted all input of procedures to mixed tuples. This caused some procedures to behave differently when called from a language interface than when called from HDevelop. Now, regions with multiple unconnected components can be evaluated as well. Thus, they are not printed to the standard output anymore. Now, multiple matches are returned in this case. Additionally, attributes that were not present in all input object models were removed.
Note that this change affects the compatibility. Read more. Now, the error "Number of input points too large" is returned in this case. Please note that only the error message and the error number have been changed. Note that this problem had no effect on the bar code reading.
Furthermore, this could have led to an undefined behavior. Other functionality that processes poses might have been affected as well in case of very large rotation values. Other operators that fit ellipses might have been affected as well, e. Now, the error "KNN is not trained" is returned to inform the user that the classifier has not been trained yet. The ECC data code reader could have crashed in very rare cases if the image contained a damaged code.
The ECC data code reader sometimes used a slightly wrong code region for decoding and print quality inspection. The operators that belong to the 2D data code reader and to the 2D metrology model could have crashed when running out of memory. Now, they return the error "Not enough memory available" instead. The Aztec code reader in very rare cases accessed invalid memory locations.
The Aztec code reader could have crashed if the width or height of the image was 1. The Aztec code reader may have crashed in very rare cases. This led also to a wrong formular in the corresponding reference manual entry.
This affected PNG images, for which the original image had a bit depth other than 8 bit or 16 bit. The 'File' interface failed to read images stored in the hobj format. Now, in this case zero is returned for the ellipse parameters. Additionally, the operator would raise an unexpected exception if called with empty tuples for rows, columns, and gray values. Additionally, an explicit error is returned when setting a single gray value for multiple pixels on an image with multiple channels that require a different number of gray values.
For example, in some cases, a score value of almost 1. Measure The operators that belong to the 2D data code reader and to the 2D metrology model could have crashed when running out of memory.
Memory Turning off the temporary memory cache did not flush the temporary memory caches of all threads in the thread pool. This led to the problem that this value was not proposed by HDevelop's auto completion. Innovative techniques, faster processing, faster development — HALCON 12 provides many great new features for all machine vision users.
Further speedup is achieved in HDevelop and HDevEngine where the execution of procedures has become considerably faster by utilizing a just-in-time compiler. HALCON's comprehensive 3D vision features were further enhanced: With the new local deformable surfaced-based matching, bent or stretched objects like pretzels can be found reliably, thus expanding the possibilities of 3D vision applications.
As a special key feature for software developers, a new extension allows to inspect HALCON variables tuples and iconic directly within Visual Studio, thus easing debugging tasks tremendously.
Characters of any size are found robustly, in most cases without the need to adjust parameters. Also, the reference manual entry has been clarified and extended. The Data Matrix ECC code reader could have accessed invalid memory when reading invalid content of symbols.
The Aztec code reader could have crashed in very rare cases. To be consistent with the other code readers, this restriction has been removed. GetCurrentDir to crash. This problem has been fixed for path lengths up to characters. This problem has been fixed: a proper error code is returned in this case.
When the timeout functionality is used, shape-based matching and the Sobel filter HALCON embedded only either could have run into a deadlock or could have used unreasonable timeout values in very rare cases. Now, the operator might be slower in some cases. Now, instead of throwing an error the first image channel is used for text segmentation. Parallelization The automatic operator parallelization AOP has had a memory leak on channel level for operators that support AOP on tuple level as well as on channel level and have more than one iconic input parameter.
After disabling and enabling compute devices, there was a small memory leak when calling operators with automatic operator parallelization. It also caused a memory leak in other rare cases. The Serialize member functions in the. NET interfaces crashed in rare cases. Image Acquisition Interfaces The latest information about new interface revisions and newly supported image acquisition devices can be found on MVTec's web server.
HALCON was unable to verify the signature of license files containing unknown modules, flags or platforms, which made the licenses non-forward compatible.
Release Notes. Cookie Settings Essential. External Content. Accept all Accept only essential Save and Close.
0コメント