Changes in doc/ref/gpu/gpu_computations.rst [066f296:711f17e] in sasmodels
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
doc/ref/gpu/gpu_computations.rst
r066f296 r711f17e 8 8 9 9 To run on the GPU, your computer must have OpenCL drivers installed. 10 For information about OpenCL installation see th e11 :ref:`opencl-installation` documentation10 For information about OpenCL installation see this 11 :ref:`opencl-installation` guidance. 12 12 13 13 Where the model is evaluated is a little bit complicated. … … 16 16 on the CPU. If the OpenCL driver is not available for the CPU then 17 17 it will run as a normal program on the CPU. 18 18 19 For models with a large number of parameters or with a lot of code, 19 20 the GPU may be too small to run the program effectively. 20 21 In this case, you should try simplifying the model, maybe breaking it 21 into several different mod els so that you don't need ifstatements in your code.22 into several different modules so that you don't need *IF* statements in your code. 22 23 If it is still too big, you can set *opencl=False* in the model file and 23 24 the model will only run as a normal program on the CPU. 24 25 This will not usually be necessary. 25 26 27 Device Selection 28 ................ 26 29 If you have multiple GPU devices you can tell SasView which device to use. 27 30 By default, SasView looks for one GPU and one CPU device 28 31 from available OpenCL platforms. 29 32 30 It prefers AMD or NVIDIA drivers for GPU, and prefers Intel or 31 Apple drivers for CPU. 32 Both GPU and CPU are included on the assumption that CPU is always available 33 and supports double precision. 33 SasView prefers AMD or NVIDIA drivers for GPU, and prefers Intel or 34 Apple drivers for CPU. Both GPU and CPU are included on the assumption that CPU 35 is always available and supports double precision. 34 36 35 37 The device order is important: GPU is checked before CPU on the assumption that 36 38 it will be faster. By examining ~/sasview.log you can see which device SasView 37 39 chose to run the model. 40 38 41 If you don't want to use OpenCL, you can set *SAS_OPENCL=None* 39 42 in the environment, and it will only use normal programs. 43 40 44 If you want to use one of the other devices, you can run the following 41 45 from the python console in SasView:: … … 48 52 Use that value as the value of *SAS_OPENCL*. 49 53 54 Compiler Selection 55 .................. 50 56 For models run as normal programs, you may need to specify a compiler. 51 57 This is done using the SAS_COMPILER environment variable. … … 54 60 TinyCC is provided with SasView so that is the default. 55 61 If you want one of the other compilers, be sure to have it available 56 on the path so SasView can find it. 62 in your *PATH* so SasView can find it! 63 64 65 .. note:: 66 This help document was last changed by Steve King, 08Oct2016
Note: See TracChangeset
for help on using the changeset viewer.