Posts by CarmenZ

    Dear Bingnan,


    please find atatched the updated design. In this design the small circle is detected

    Following improvements are implemented:

    1. The number of fractional bits for division by number "K" is increased to 10 fractional bits

    2. In module "SigmaI" a module to avoid division by zereo is added.


    The changes are marked in yellow in the following screnshot.


    pasted-from-clipboard.png


    Concerning comment #15: The size of the template is only limited by the FPGA resources. You may change the upper limit of the operator IntParamTranslator "TranslateK" if FPGA resources allow a bigger template.

    Dear Jayasuriya,


    the DMAFromPC operator is only available on VD1/VD4 frame grabbers. For the microEnable 5 series frame grabber there is no alternative.

    Dear Bingnan,

    In the design attachment of Comment 9, some of the FIR operator values in module "Sigma_I" were 0 due to the kernel extension to 15x16 pixels. Please find in the attachment the updated design. With adjustment of the threshold for visualization the middle of the circle objects are visible. However at the botom and top of the input images also matchings are found. I assume this is because of the background contained in the template objects.

    Dear Bingnan,


    thank you for the description of the problem and the VisualApplets design with the corresponding images. I had a look in your design and found that the content of the FIRoperators "Rmean_Mult_K" and "Sum_RxR" are not adapted to your template image. These operators need to be adapted as well as the threshold for visualization. Please see details in the comment box on the top level of the design and under https://docs.baslerweb.com/vis…izedCrossCorrelation.html



    pasted-from-clipboard.png

    Dear Pier,


    may you please try the follwong: Please add an empty process to the VA design. Build it and start the hardware test again. How is the behaviour now?

    Dear Pier,


    let me summarize the problem you observe:


    You have tested the design in hardware. With camera 0 you can acquire, but with camera 1 you get no image, but a timeout. Is this correct? What happens if you exchange the cameras physically? Does the camera , which originally did not acquire images, work now?

    Dear Ih Shin,


    the error for the operator "FrameBufferRandomRead" (DRAM) is due to the different data width per RAM for the "microEnable 5 ironman VD8-PoCL" platform in comparison to the marathon VCL platform. For the marathon VCL platform it is 256 bit, for the "microEnable 5 ironman VD8-PoCL" platform it is 128 bit. Please see also the documentation for operator "FrameBufferRandomRead" under https://docs.baslerweb.com/vis…rameBufferRandomRead.html

    and the device resources under https://docs.baslerweb.com/vis…t/device%20resources.html. The distortion correction example is designed for the marathon VCL platform with 256 bit per RAM. Please find attached the design adapted for the "microEnable 5 ironman VD8-PoCL" platform.

    Dear Baoxi,

    please find attached a ViausalApplets design example, for the definition of a round central region. The idea of the design is to go in a coordinate system reletive to the image center, and calculate the distance of the current position relative to the center of the image. Then we can set all pixels outside a specific radius to value zero.

    Files

    Dear Baoxi,


    thank you for your answer. As the region of interest is a circle I have some additional questions:

    1. Do you know the coordinates x and y, where there is useful or useless information without further image processing?

    2. Is it suitable for you to do a filtering by setting the useless pixel to zero value?


    If yes, you can think of a processing like sketched in the following:

    pasted-from-clipboard.png


    With this processing you can set all pixels outside a specified region to a zero value. You also can combine this processing with a previous selection of a rectangular region of interest for example using operators SelectROI, DynamicROI,....

    Dear Danna,

    thank you for your question.

    Please find under "...\Examples\Processing\Color\bayer" in your VisualApplets installation directory multiple examples for Bayer demosaicing. Under https://docs.baslerweb.com/liv…ent/bayer%20Overview.html you can find a detailed description for these examples.

    Under "...\Examples\Processing\..." in you VisualApplets installation directory there are more image processing examples which might be of interest for you: E.g. examples for image composition ("..\Examples\Processing\HDR_ImageComposition") . Under "..Examples\Acquisition\BasicAcquisition\..." you can find examples for basic image acquisition designs.

    Dear Sangrae Kim,

    under "\examples\Processing\Geometry\GeometricTransformation\DistortionCorrection.va" in your VisualApplets installation directory you can find an example for distortion correction implementation. This example is based on the OpenCV implementation for the determination for the correction coefficients. Please find a detailed description on this example under https://docs.baslerweb.com/liv…l#Distortion%20Correction.

    Dear Saito-san,

    thank you for the question. You may use a "LineMemory" operator as it is used in the VisualApplets example "TapSorting_8X_1Y.va" under "Examples\Processing\Geometry\TapGeometrySorting" in the VisualApplets installation directory.

    Dear Saito-san,


    thank you for your question.

    I had a look on the description of Halcon function "fit_surface_first_order" (https://www.mvtec.com/doc/halc…_surface_first_order.html ) : This function approximates a first order surface plane to a gray value object in minimizing the distance between gray values and plane. Also the gray value moments are calculated.

    I think such functionality can be implemented in VisualApplets using loop functionality and a geoemetric scaling function within this loop to approximate a plane to an object.


    Under (https://www.mvtec.com/doc/halc…n/moments_gray_plane.html.) I found a similar Halcon function : "moments_gray_plane". It also calculates the gray value image moments and approximates a plane. Only method for plane claculation is different. As it seems from description it maybe possible to implement in Visual Applets without loop functionality. Is this method also of interest for the customer?

    Dear JSuriya,

    thank you for your request.

    Do you refer to the Visual Applets example "PrintInspection_Blob.va"?

    Please may you explain "reference points"? Do you mean rotation, translation and scaling with respect to a certain point (E.g center of gravity)?

    Of cource instead of rotation around center of gravity you can choose any other point in the image to perform the transformation.