The openvx specification_ introduction

OpenVX is a low-level programming framework domain to enable software developers to efficiently access computer vision hardware acceleration with both functional and performance portability. Data recovery software OpenVX has been designed to support modern hardware architectures, such as mobile and embedded SoCs as well as desktop systems. Data recovery advisor Many of these systems are parallel and heterogeneous: containing multiple processor types including multi-core CPUs, DSP subsystems, GPUs, dedicated vision computing fabrics as well as hardwired functionality.

Database host name Additionally, vision system memory hierarchies can often be complex, distributed, and not fully coherent. Database performance OpenVX is designed to maximize functional and performance portability across these diverse hardware platforms, providing a computer vision framework that efficiently addresses current and future hardware architectures with minimal impact on applications.

OpenVX defines a C Application Programming Interface (API) for building, verifying, and coordinating graph execution, as well as for accessing memory objects. Data recovery broken hard drive The graph abstraction enables OpenVX implementers to optimize the execution of the graph for the underlying acceleration architecture.

OpenVX also defines the vxu utility library, which exposes each OpenVX predefined function as a directly callable C function, without the need for first creating a graph. Database xe Applications built using the vxu library do not benefit from the optimizations enabled by graphs; however, the vxu library can be useful as the simplest way to use OpenVX and as first step in porting existing vision applications.

As the computer vision domain is still rapidly evolving, OpenVX provides an extensibility mechanism to enable developer-defined functions to be added to the application graph.

The document contains the definition of the OpenVX API. Database yml mysql Tthe conformance tests that are used to determine whether an implementation is consistent to this specification are defined separately.

The section “Module Documentation” forms the normative part of the specification. 5 database is locked Each API definition provided in that chapter has certain preconditions and post conditions specified that are normative. Database fundamentals If these normative conditions are not met, the behavior of the function is undefined.

In this specification, the words shall or must express a requirement that is binding, should expresses design goals or recommended actions, and may expresses an allowed behavior.

This minimizes the possibility of name collisions and promotes sorting and readability when querying the namespace of available vision functions. Database concepts Each vision function should have a unique dotted name of the style: tld.vendor.library.function. Database icon The hierarchy of such vision function namespaces is undefined outside the subdomain “org.khronos”, but they do follow existing international standards. Database versioning For OpenVX-specified vision functions, the “function” section of the unique name does not use camel case and uses underscores to separate words.

• Atomic: The specification mentions atomics, which means a C primitive data type. Database 2013 Usages that have additional wording, such as atomic operations do not carry this meaning.

• Kernel: OpenVX uses the term kernel to mean an abstract computer vision function, not an Operating System kernel. Database cursor Kernel may also refer to a set of convolution coefficients in some computer vision literature (e.g., the Sobel “kernel”). Database list OpenVX does not use this meaning. Database queries must be OpenCL uses kernel (specifically cl_kernel) to qualify a function written in “CL” which the OpenCL may invoke directly. Database journal This is close to the meaning OpenVX uses; however, OpenVX does not define a language.

This specification would not be possible without the contributions from this partial list of the following individuals from the Khronos Working Group and the companies that they represented at the time: