From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
From Friday, April 19th (11:00 PM CDT) through Saturday, April 20th (2:00 PM CDT), 2024, ni.com will undergo system upgrades that may result in temporary service interruption.
We appreciate your patience as we improve our online experience.
04-05-2011 08:20 AM
Hey Evan D.
I am using the IMAQ Correlate VI in the LABVIEW Student Edition 2009.
and i have a 'little' two questions for you:
1> The above mentioned VI outputs an image scaled from 0 till 255, depending on the degree of matching; my question is: how did they obtain these values,
i used the formulas attached and i obtained values from -1 to 1.
2>where bugs fixed in IMAQ Correlate VI (bugs mentioned by Root Canal ) in LABVIEW 2010 Student Edition.
Best Regards
M. Sleiman
Electrical Engineer
YL-Engineering
04-05-2011 01:03 PM - edited 04-05-2011 01:07 PM
1. The output is just rescaled from [-1, 1] to [0, 255]
2. The bugs seem to be fixed. A direct method and the IMAQ Correlate produce very similar but not exact results now.
04-05-2011 05:20 PM
Thanks Randall
04-07-2011 03:34 AM
Here's my VI's....
thanks RC.
M.Sleiman
12-10-2013 03:23 PM
I would debate whether this VI has been fixed yet or not. I am enclosing a VI where I take an array and a kernal, convolve them using the Convolution vi, then convert the array to an IMAQ and again convolve with the kernal but using the IMAQ Convolute vi, yielding a notably different result. I would be interested to hear if there is a bug in my code or if it's still in the IMAQ Convolute vi.
Teresa
12-10-2013 03:26 PM
Just noticed this threat was about correlate and not convolute. I suspect there is a problem with the 2d convolution IMAQ vi though.
12-11-2013 03:38 PM
Hi tgmiller,
What versions of LabVIEW, Vision Acquisition Software, and Vision Development Module are you using?
12-11-2013 03:45 PM
I'm using Labview 2010 SP1, Vision Dev 2010 SP1 and, Vsion Acq August 2010.
My coworker believes the problem is likely to be something to do with how the borders are treated by each convolution. If that is the case then I wish there were better documentation on these two functions because I really think that a 2D conv that takes the same inputs and returns an output of the same sizes should give the same result unless clearly stated why it will not in the documentation.
Thanks,
Teresa
12-16-2013 01:05 PM
Thank you for providing that information. I will file a bug request for this and forward it to our R&D team.