• 04/03/2020
  • Public Content

Difference in Interpretation of the OpenCV and OpenVX* Parameters

When porting from OpenCV to OpenVX* there are cases of straightforward parameter matching between the APIs. However there are cases when the parameter meaning is different. For example, both OpenCV and OpenVX offer
functions, but with the following subtleties:
  • OpenVX's
    implement the
    cv::WARP_INVERSE_MAP flavor
    of the corresponding OpenCV calls.
  • OpenCV and OpenVX uses different formulas to access transformation matrix. In order to convert transformation matrix for OpenVX, the OpenCV matrix must be transposed.
Similarly the OpenCV’s Filter2D and OpenVX’s Convolution are both filtering routines that can be used interchangeably along with the following:
  • OpenVX Convolution formula differs from OpenCV's
    . In order to get the same result in OpenVX the original OpenCV “kernel” parameter must be flipped around both axises.
  • OpenVX Convolution uses 16-bit signed integer data type for “kernel” parameter, along with additional scale parameter, so which, when calling the OpenCV’s need to be converted accordingly.

Product and Performance Information


Intel's compilers may or may not optimize to the same degree for non-Intel microprocessors for optimizations that are not unique to Intel microprocessors. These optimizations include SSE2, SSE3, and SSSE3 instruction sets and other optimizations. Intel does not guarantee the availability, functionality, or effectiveness of any optimization on microprocessors not manufactured by Intel. Microprocessor-dependent optimizations in this product are intended for use with Intel microprocessors. Certain optimizations not specific to Intel microarchitecture are reserved for Intel microprocessors. Please refer to the applicable product User and Reference Guides for more information regarding the specific instruction sets covered by this notice.

Notice revision #20110804