From c4c8983b38413745f6bd869c6e6f500579b00e64 Mon Sep 17 00:00:00 2001 From: Sadaf Ebrahimi Date: Thu, 16 May 2024 20:36:19 +0000 Subject: Remove ImageMagick Please go through go/android-3p process if you need this project in the future. Bug: 155434586 Test: TreeHugger Change-Id: Ie00c117806c45dd13eefdce3ef123833148c6fbb --- www/opencl.html | 153 -------------------------------------------------------- 1 file changed, 153 deletions(-) delete mode 100644 www/opencl.html (limited to 'www/opencl.html') diff --git a/www/opencl.html b/www/opencl.html deleted file mode 100644 index 4bf126efc..000000000 --- a/www/opencl.html +++ /dev/null @@ -1,153 +0,0 @@ - - - - - - - - - - ImageMagick - Parallel Execution with OpenCL - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
- - - - -
- -
-
-
- -

The following is a list of image operators that have been OpenCL-accelerated:

-
blur
-charcoal
-contrast
-constrast-stretch
-convolve
-despeckle
-edge
-equalize
-emboss
-function
-gaussian-blur
-grayscale
-modulate
-motion-blur
-negate
-noise
-radial-blur
-resize
-sketch
-unsharp
-

When the OpenCL acceleration is invoked for the first time, ImageMagick conducts a series of tests to configure the OpenCL environment according to the system hardware; therefore, it is normal to experience a higher latency the first time you use an accelerated option. The OpenCL kernels are embedded inside ImageMagick in source format. During the initial setup, ImageMagick discovers all the available OpenCL devices and compiles the kernels for each of these targets. ImageMagick also runs several performance tests internally to determine the preferred device to use. The compiled kernel code and the performance test results are stored into the cache directory so that the data can be reused by subsequent invocations of the OpenCL path. By default, the OpenCL cached data is stored in $HOME/.cache/ImageMagick on Linux and on MacOSX or in %LOCALAPPDATA%\ImageMagick on Windows. To change the cache directory, set the MAGICK_OPENCL_CACHE_DIR environment variable. ImageMagick is able to detect hardware changes, driver updates, and new kernel sources and re-run the setup and the calibration test. You can also force ImageMagick to re-run the process by removing the content from the cache directory.

-

If ImageMagick includes OpenCL support, the OpenCL path is enable by default. You can disable it, simply set the environment variable MAGICK_OCL_DEVICE to OFF. You could also force the OpenCL path to use a particular class of devices by setting it to GPU or CPU.

-

In addition to the environment variables just mentioned, ImageMagick provides a set of APIs that allow developers to gain a finer grain control of the OpenCL acceleration. For example, use the InitializeOpenCL) function to initialize the OpenCL environment:

-
clEnv=GetCurrentOpenCLEnv();
-if (InitializeOpenCL(clEnv,exception) == MagickFalse)
-  {
-    /* looks like OpenCL is not supported  */
-  }
-
-
-
- - - - - - - \ No newline at end of file -- cgit v1.2.3