Ignore:
File:
1 edited

Legend:

Unmodified
Added
Removed
  • doc/ref/gpu/gpu_computations.rst

    r066f296 r711f17e  
    88 
    99To run on the GPU, your computer must have OpenCL drivers installed. 
    10 For information about OpenCL installation see the 
    11 :ref:`opencl-installation` documentation 
     10For information about OpenCL installation see this 
     11:ref:`opencl-installation` guidance. 
    1212 
    1313Where the model is evaluated is a little bit complicated. 
     
    1616on the CPU.  If the OpenCL driver is not available for the CPU then 
    1717it will run as a normal program on the CPU. 
     18 
    1819For models with a large number of parameters or with a lot of code, 
    1920the GPU may be too small to run the program effectively. 
    2021In this case, you should try simplifying the model, maybe breaking it 
    21 into several different models so that you don't need if statements in your code. 
     22into several different modules so that you don't need *IF* statements in your code. 
    2223If it is still too big, you can set *opencl=False* in the model file and 
    2324the model will only run as a normal program on the CPU. 
    2425This will not usually be necessary. 
    2526 
     27Device Selection 
     28................ 
    2629If you have multiple GPU devices you can tell SasView which device to use. 
    2730By default, SasView looks for one GPU and one CPU device 
    2831from available OpenCL platforms. 
    2932 
    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. 
     33SasView prefers AMD or NVIDIA drivers for GPU, and prefers Intel or 
     34Apple drivers for CPU. Both GPU and CPU are included on the assumption that CPU  
     35is always available and supports double precision. 
    3436 
    3537The device order is important: GPU is checked before CPU on the assumption that 
    3638it will be faster. By examining ~/sasview.log you can see which device SasView 
    3739chose to run the model. 
     40 
    3841If you don't want to use OpenCL, you can set *SAS_OPENCL=None* 
    3942in the environment, and it will only use normal programs. 
     43 
    4044If you want to use one of the other devices, you can run the following 
    4145from the python console in SasView:: 
     
    4852Use that value as the value of *SAS_OPENCL*. 
    4953 
     54Compiler Selection 
     55.................. 
    5056For models run as normal programs, you may need to specify a compiler. 
    5157This is done using the SAS_COMPILER environment variable. 
     
    5460TinyCC is provided with SasView so that is the default. 
    5561If you want one of the other compilers, be sure to have it available 
    56 on the path so SasView can find it. 
     62in 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.