Confirmed users
770
edits
User talk:Dead project: Difference between revisions
Jump to navigation
Jump to search
→WebImage:
(→Kaku) |
|||
| Line 67: | Line 67: | ||
==WebImage:== | ==WebImage:== | ||
Why do we need WebImage? Because performance is matter to prompt computer vision to the Web. We need it for performance reason. Most image processing task can be accelerated by WebGL. But it is not the case for computer vision area. So we need a hardware accelerated-able computer vision related web API to help Web developer deliver a fast and portable Web page and application. That is the motivation of WebImage. | |||
<br> | |||
This is a new zone needed to explore. So we might start from refer to existing related API. In end of 2014, KHRONOS released a portable, power efficient vision processing API, called OpenVX. This specification might be a good start point for WebImage. | |||
<br> | |||
The following diagram is a brief concept of OpenVX. It is a graph-node architecture. The role of OpenVX for computer vision is like the role of OpenGL for graph. The developer just construct and execute the graph to process incoming image. | |||
<br> | <br> | ||
[[File:OpenVX-NodeGFX.PNG|600px]]<br> | |||
<!--[[File:Project FoxEyeWebImage1.png|800px]]<br>--> | <!--[[File:Project FoxEyeWebImage1.png|800px]]<br>--> | ||
OpenVX can be implemented by OpenCL, OpenGL|ES with compute shader and C/C++ with SIMD. That means we can support OpenVX in wide range Web platform from PC to mobile once a OpenVX engine is provided. | |||
[[File:OpenVX.PNG|600px]]<br> | [[File:OpenVX.PNG|600px]]<br> | ||